• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Form Button as Primary Key call program bug

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

  • Form Button as Primary Key call program bug

    Version 6.3.20250910

    I have a simple pop up form with a save button set as the primary key. It calls an RPG pgm and on success hides the pop up and refreshed grid that is affected.

    image.png?

    ??
    There's an issue when I hit the enter key fast enough, it calls the RPG pgm that many times. If i press the enter key2-3 times before the pgm returns success true/false it'll, in my case, create 3 records.

    image.png?
    image.png?
    ?
    Should the primary button only be called once until it returns success true/false?

    Thanks
    Attached Files

  • #2
    We will take a look into this and get back to you.

    Comment


    • #3
      Trying to think of the best approach here. The "form" has no idea what happens after the button is clicked so it does not know to wait for a response from a back end program. Additionally, you could make a case that there are use cases where you would not want to wait for the response before allowing more actions.

      So I would recommend the following (I just tried this and it works).
      • Create a new app variable to disable your primary button
      • Link the new app variable to the Disable property of the button
      • On the click of the button, set your app variable to "true" (to disable the button)
      • Set the app variable to "false" on the success or false response from the Call RPG Program action.

      Comment

      Working...
      X