• 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 Error not displayed when form shows for the 1st time

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

  • Form Error not displayed when form shows for the 1st time

    Reference: https://forums.cnxcorp.com/web/forum...or-date-picker

    We have a app where we are loading form using button program and "SetResponse('formFieldValueSilent'" option and in behaviours we use Show with Keep data option.
    In the button program itself we are also displaying the errors below the fields using "SetResponse('formFieldError'"

    The issue is when we are loading the form for the 1st time and if there is some error to be displayed, the error does not get displayed.
    if we go back and come again for the same record then it shows the error correctly.

    Error should have been displayed but it didn't
    image.png?
    I went back and came again the error is displayed and now it starts working fine
    image.png?

  • #2
    When and how does the application show the form widget?
    • Is it displayed after the button program call is successful?
    • Is it shown via a filter widget, or only from a "Show Section"?
    We need more details of this type to investigate further. Thanks!

    Comment


    • #3
      Behavior:
      • The app opens with a Grid displaying multiple rows.
      • On row click, a program is triggered that uses SetResponse to Load form field values and any associated errors.
      • The form is shown with keep data option.
      Issue:
      • When the app is opened for the first time, if you click on a row that has an error, the error does NOT display on the form initially.
      • If you navigate back to the main grid and click the same record again, the error appears correctly.
      • From this point onward, the error display works fine for all subsequent clicks until the app is closed.
      • This behavior is consistent across multiple applications using a similar process. The savefile i sent you earlier also has the same issue.
      • The current app provides the easiest scenario to reproduce the issue.

      Comment

      Working...
      X