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



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

Refresh calling UX after Grid Called from UX

  • Filter
  • Time
  • Show
Clear All
new posts

  • Refresh calling UX after Grid Called from UX

    I have a UX component. From it, i call a Grid and do some updates.
    After I close the grid, I'd like to perform an action (refresh the data) on the UX.

    Question, is there an event that is triggered within the UX when focus is back on the UX ?

    Thanks, Dave

  • #2
    Re: Refresh calling UX after Grid Called from UX

    Hey Dave, if you are opening the grid in a window, you can use the window javascript event (onHide) to execute javascript when the window closes.
    This is accessible from the Open Grid property window.
    You can also call javascript to refresh the ux when updating your records in the grid.

    To execute a function on your ux from the child grid, you will need to get a pointer to the parent object:
    var po = {dialog.object}.getParentObject();
    Good luck.
    Nate Mitchell PMP


    • #3
      Re: Refresh calling UX after Grid Called from UX

      Hi Nate, thanks so much! I'll check this out now!


      • #4
        Re: Refresh calling UX after Grid Called from UX

        No problem.
        If you run into issues, let us know what you are attempting to update on the parent ux and we'll be able to provide additional details.
        Nate Mitchell PMP


        • #5
          Re: Refresh calling UX after Grid Called from UX

          Nate, thanks just never was in the details of the calling grid window area. Works great.
          Typically, what do you execute to refresh the current UX record (set of records)? I have been refreshing the keys, which you then need to determine the order of the records to be presented, but I'd prefer simply to refresh the given record...
          Thanks so much.


          • #6
            Re: Refresh calling UX after Grid Called from UX

            With a data bound ux, when I need to pull up a new record, I will call the following method, where sID is the primary key for the record.

            var data = '__sID__';
            {dialog.object}.populateControlsFromTable(data,false,'','PLACEHOLDER_1','<Default>',{"showWaitMessage": false});
            I'm not sure I understand however why you would want to update a record both in a parent ux and in a child grid.
            What you may want to consider doing is showing your records in a list control on the parent, and then opening a child ux to edit the detail.
            In this case, you would simply need to refresh the list when any edits are committed.

            Even if you need to stick to this design pattern, I would highly recommend moving your grid to a list control.
            If you are not mobile now, chances are you will need to be at some point.
            Just a thought.
            Nate Mitchell PMP


            • #7
              Re: Refresh calling UX after Grid Called from UX

              I have items of an order in the repeating section of the UX. I also have sub-items within each of the items on the UX. I am updating these subitems within a grid call. Based on the subitem changes, The price for the item in question will change, therefore I need to refresh the ux to show the result of the sub items... make sense?


              • #8
                Re: Refresh calling UX after Grid Called from UX

                I wasn't sure how to update the subitems as part of the UX, so created separate grid linked to the order to update these subitems.... maybe there is a way to incorporate these subitems into the ux, under the items...


                • #9
                  Re: Refresh calling UX after Grid Called from UX

                  By the way, this has worked out perfectly, thanks so much for your help!
                  Any other thoughts just let me know regarding my comments about the tables managed outside the UX.


                  • #10
                    Re: Refresh calling UX after Grid Called from UX

                    That does make sense Dave and I can see how you came up with that design.
                    Glad it is working for you.

                    If you want to look at an alternative, cascading lists may work for you as well.
                    Your current repeating section would be 1 list and your sub items a child list.

                    Search for cascading list from the video library:


                    If you run into any problems with either approach, let us know.
                    Nate Mitchell PMP


                    • #11
                      Re: Refresh calling UX after Grid Called from UX

                      Thanks a ton Nate!

                      One quick question...

                      If I'm working with a parent child (order - item) UX...

                      Say I update the child (item) table, and I update some stuff on the backend through SQL Server trigger. WIthin this trigger, I update some data on the parent (order) record.

                      What approach would you use to have re-fetch the data for the parent table so I see the updates made in the trigger?

                      (As I see it, if I only update the child table, only the child table is refreshed after a submit, I'd like the parent to also be refreshed...



                      • #12
                        Re: Refresh calling UX after Grid Called from UX

                        Great question Dave.
                        Using triggers may pose a challenge for you on the refresh, as you could run into timing issues.
                        It will all depend on your trigger logic and what your testing shows.
                        In the case of parent/child list controls, you can execute refresh methods on both when you make a change.
                        However, depending on your trigger logic, your trigger sql may not complete by the time the parent list is refreshed.

                        If your trigger logic executes quick enough, this may not be an issue.

                        If it becomes and issue, you can use a javascript setTimeout method to wait to execute your refresh commands after submit.

                        I'm a sql guy, so for dependent updates like this, I handle the submit myself and pass my updated values into a sql stored procedure and deal with the parent/child sql updates manually. That way, I know when the server side logic has completed and I can then tell the client when to process the refresh.

                        I'm curious if others have different thoughts on this.
                        Nate Mitchell PMP


                        • #13
                          Re: Refresh calling UX after Grid Called from UX

                          I ended up refreshing the keys and popping the updated key to keep the order in focus... thanks so much for taking the time to help me, I actually learned a lot and am making some progress... :)