Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Callback Receiving Old Data

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Callback Receiving Old Data

    OK, stipulating to the fact that this could easily be pilot error, I'm seeing an issue that I can't seem to figure out.

    I have a read-only grid with an editable detail part. To accomplish what I need I've created a callback calculation routine, a javascript action to call that routine and, in the OnDetailViewRender server-side event of the grid, I return javascript to run that action. The callback needs the value of a couple of fields in the detail part and then returns javascript to set other fields with the result. To give the callback the required information, instead of selecting "Compute current row data" in the Action Javascript dialog, I've created a javascript function which I put in the "Additional Data to Submit" field. The function reads the values from the detail part using getValue.

    So far, so good. Everything fires when it's supposed to. The callback (with the exception I'm about to note) gets the data it needs, does its calculations and is able to return javascript to set the appropriate field(s) on the detail form. The problem is the following: If I CHANGE the value of one of the fields that the javascript function is accessing with getValue, then click "Save", the variable sent to the callback contain the PREVIOUS value of the field. That is, if, say, I change "Rate" from .90 to 1.00, then click Save, the callback (which is definitely triggered AFTER the data has been saved), gets .90 instead of 1.00. The 1.00 shows in the "Rate" field in the detail form; if I set an OnChange event handler for the "Rate" field to do a getValue and display the return value in an alert, I see 1.00. I have no idea why the callback is getting .90.

    Again, it could easily be pilot error (either a lack of understanding of the fundamentals or a coding error), but I've cobbled up a small test case to exhibit the problem (it's called setValue because I was too lazy to change the name of the test case I posted previously).

    Any ideas would be gratefully accepted.

    BTW, I'm using 3550-4650.
    Attached Files

    #2
    Re: Callback Receiving Old Data

    You can try putting it here: CanUpdateRecord

    q = datasubmitted.QUANTITY
    r = datasubmitted.rate
    CalcResult = convert_Type(q,"n") / convert_Type(r,"n")

    Comment


      #3
      Re: Callback Receiving Old Data

      Or if you have a column that you are saving it to you can use a Calculated field expression and just put Quantity / Rate. This will display on screen and also save it when you save.

      Comment


        #4
        Re: Callback Receiving Old Data

        Although you give an excellent explanation of what you're doing and an excellent test case, I'm not sure what you're trying to achieve. Once you have this working, is your plan to do something more involved at the server with any calculations? If not, then your current methodology is far too complex and extremely wasteful.

        What you're doing, in effect, is this.

        Rendering the detail view on the client side... and when that's done you're sending a message to the server to run an action... on the client side. That action performs an ajax callback... heading back to the server... to calculate a value using 2 numbers you already had at the client side, and send that calc back to the client.

        That's like you and I standing beside each other... and you handing me a calculator and asking me to run down the street and give it to our friend, Bob... and ask him to bring it back to you. So I run down the street, give the calculator to Bob and ask him to run it back up the street to you. He does this. You then tell Bob that Quantity = 9101 and Rate = 1, hand Bob the calculator and ask him to run down the street and give everything to me and ask me to bring everything back to you. So... Bob runs down the street, gives and tells me everything and I run back up the street and tell you and give you back the calculator. But, you already knew everything and already had the calculator... so you actually had everybody running around for nothing... in which case Bob and I go off for pizza shaking our heads.

        You want to calculate Mileage which is Quantity / Rate. In the Query section of the Grid I added a Calculated field... mileage = quantity/rate. I then added this field to the Detail Section. Now when I change the Rate and save, the Calculated field is automatically updated with the correct and current value. Granted, because you're saving stuff, the calc is being passed back to the client.

        You don't have to use a Calculated field. You could do this all client side, if you don't need anything from the server. It depends on what you want to do with the calculated data.

        Is that all you want to achieve? Or is it more complex than that.

        Comment

        Working...
        X