Until v20250914.1 everything was working fine for my application.
Starting from v20250920.1 I started seeing serious problems with some of my tables. Specifically those are "legacy" tables (pre-existing, defined as read-only in my application).
With the help of AI I finally found out how to understand and overcome the problem.
Looks like the new default validators since v20250920.1 cannot handle "empty" values properly for reference columns, which results in an error.
The workaround is to add an explicit validator to all the reference columns:
requires=[IS_EMPTY_OR(Validator())]
Looks to me that this should already be the default for those validators. Empty fields (if allowed in the table setup) do not need any validation.
Until v20250914.1 everything was working fine for my application.
Starting from v20250920.1 I started seeing serious problems with some of my tables. Specifically those are "legacy" tables (pre-existing, defined as read-only in my application).
With the help of AI I finally found out how to understand and overcome the problem.
Looks like the new default validators since v20250920.1 cannot handle "empty" values properly for reference columns, which results in an error.
The workaround is to add an explicit validator to all the reference columns:
requires=[IS_EMPTY_OR(Validator())]Looks to me that this should already be the default for those validators. Empty fields (if allowed in the table setup) do not need any validation.