IntegerField is not giving error in first place if the value entered is text

Hi viveku0001,

I suggest you to use the parameter called "Refresh After" and the valid value for the parameter in your case must be "KEYPRESS",which means it refreshes after every character typed into the field.
If the user deselects the field after changing its value you can use "UNFOCUS" which is considered as a default value.

Hello Ravalik,

Its still the same, I think refreshAfter is just to decide when do we need the values to be saved after keypress or unfocus but here in my case the issue is related to error message that is not poping up if user enters any text value in numeric field at first instance instead it gets cleared out and again if we enter any non numeric value only then the message pops up.

Hi viveku0001,

Can you please go through it.

Hi Ravalik,

As I said I already tried KEYPRESS but still getting the same response. Please find the attached screenshot

Hi viveku0001,

I have tried the below code in Appian 17.4 it is throwing an error on Key press. Not sure why it is not working in your case. It should work as ravalik suggested.

 

load(
  local!a: {
    0,
    0
  },
  a!gridLayout(
    label: "Label",
    labelPosition: "ABOVE",
    headerCells: {
      a!gridLayoutHeaderCell(
        label: "Header Label"
      ),
      a!gridLayoutHeaderCell(
        label: "Header Label"
      )
    },
    columnConfigs: {},
    rows: {
      a!forEach(
        items: {
          1,
          2
        },
        expression: a!gridRowLayout(
          contents: {
            a!richTextDisplayField(
              value: a!richTextItem(
                text: "Integer",
                style: "STRONG"
              )
            ),
            a!integerField(
              label: "Label",
              labelPosition: "ABOVE",
              value: local!a[fv!index],
              saveInto: {
                local!a[fv!index]
              },
              refreshAfter: "KEYPRESS",
              validations: {}
            )
          }
        )
      )
    },
    selectionSaveInto: {},
    validations: {},
    shadeAlternateRows: true
  )
)

Hi Vimal,
I do agree that KEYPRESS should work but in my case it was not throwing the error. However, The issue is resolved now as I changed my entire code with a!applyComponents() function instead of a!foreach() and its working fine. Even I'm confused at this point why the same code is not throwing error with a!foreach and working fine with a!applyComponents() function