Announcement

Collapse
No announcement yet.

Grid reload data not working after upgrade to 6.0.20210818.0

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

  • Grid reload data not working after upgrade to 6.0.20210818.0

    Hi,

    We have a data grid with a row button that calls an edit form. After changing and saving some data on this form, the grid is shown with reload data. But the data isn't changed on the grid. Even with the refresh button the data isn't updated in the grid.
    Only after closing/reloading the app the correct data is shown.

    If we do the refresh in a browser session that didn't perform the update the grid is updated as expected.

    If we use the same form for an add record the update of the grid is performed correctly.

    Please help,
    Theo

  • #2
    Can you post a screenshot of the relevant Behaviors section? I assume that you have a button attached to your form which then calls and RPG program that waits for "success=true" to then reload your grid data?

    Comment


    • #3
      That's corrrect, we added an nabmsg to the success=true and that message is shown after the pressing the save button on the form.

      We found in chrome debug that after pressing the save button we receive the message
      URI request too large
      See attachment "uri request" for request
      Attached Files

      Comment


      • #4
        Hi Theo -

        Can you try recompiling any associated RPG programs related to this app (startup program, form helper, button click program, etc...)?

        Comment


        • #5
          Hi Sean,
          The recompile did not help for this issue.
          Theo

          Comment


          • #6
            Can you post the uri request again?

            Comment


            • #7
              I think we found the issue in a no sense statement:
              setAppVar('contractor' : getAppVar('contractor'));

              I removed this and now it seems to work. We will do some more checks and will let you know.

              Comment


              • #8
                Yep, all is working as it was, problem solved.
                Thanks for your support,
                Theo

                Comment

                Working...
                X