In reply to: Phil
We basically worked our way through it in the office and found it that it to do with "Maximum number of rows in edit mode" set to 0 instead of default 50.
Apparently it break quite a bunch of page loads and form fields if it is set that way.
Is there a reason why it is allowed to be set to 0 if it cause such a ruckus.
Dear Phil,
Thank you for reporting this issue.
We were able to reproduce the problem when the “Maximum number of rows in edit mode” parameter is set to 0 while the options to add/clone/delete rows are disabled and the action column is turned off.
We confirm that this is a bug, and a fix will be included in one of the upcoming releases.
To clarify: the ability to set the value to 0 is intentional and means there is no limit on the number of rows in edit mode (i.e., all rows can be editable).
The mechanism itself is working as designed; the problem is caused by improper handling of this particular configuration in the current version.