2009 vs. 2016 - Table OnValidate trigger called when field value does NOT change

rsaritzky · 2017-04-11

Hi all,

On a NAV2009 RTC page (e.g. General Journal), if you type in the SAME value in a field that is already there, the table's OnValidate trigger is called (even though you didn't change the value).

In NAV2016, it appears from observation that this is NOT the case. If the value is the same, then the Table's OnValidate trigger does not get called. This assumes no code in the PAGE's OnValidate trigger (e.g. the General Journal page).

Is this true? It may in fact seem logical to see this change, although it affects a custom page that we're converting from 2009->2016.

Thanks

Ron

SilverX · 2017-04-11

Yes, that's true. Mainly for performance reasons (no change, no need to validate and do a server roundtrip). You can simulate a change by adding a space before the value and leave the field, even for numeric or date fields. I use F2, Space, Tab to re-validate.

kriki · 2017-04-19

[Topic moved from 'NAV/Navision Classic Client' forum to 'NAV Three Tier' forum]

SilverX · 2017-04-11

Yes, that's true. Mainly for performance reasons (no change, no need to validate and do a server roundtrip). You can simulate a change by adding a space before the value and leave the field, even for numeric or date fields. I use F2, Space, Tab to re-validate.

rsaritzky · 2017-04-12

Carsten,

Thanks for this shortcut trick!

Ron

kriki · 2017-04-19

[Topic moved from 'NAV/Navision Classic Client' forum to 'NAV Three Tier' forum]

2009 vs. 2016 - Table OnValidate trigger called when field value does NOT change

Best Answers

Answers

Categories