Regarding this message
Where do you go to confiugre the validation settings?
Refer to https://www.laserfiche.com/support/webhelp/Laserfiche/10/en-US/administration/#../Subsystems/LfAdmin/Content/Modify_Dynamic_Fields.htm for information about the "restrict values" option for dynamic fields
Optional: The Restrict Values option determines the behavior of the field when accessed using the SDK or another application; it is not relevant if you are accessing the values through version 8.2 or later of the Laserfiche web or Windows client. If you select False, external applications will be able to save values to that field even if they do not exactly match the values in the external table. For example, if you have a Quick Fields session reading an employee name from OCR, it would be able to save that value even if it contained a small mismatch due to OCR. If you select True, the value must match the value in the external table exactly, or it cannot be saved. This value is recommended if you are using dynamic fields for data verification. If you are unsure which option to select, we recommend leaving it set to the default, False.
Aside from this option, if you're running into this error via the Windows Client while trying to set dynamic field values where it also involves multivalue field groups, then there was a bug that's fixed in version 11 and higher of the Windows Client.
Dynamic fields would be configured on the template, but there's not really a "validation" setting. I'm pretty sure a dynamic field just has to match a value in the configured data source and you'll get that error if the value you enter isn't found.
Making a field dynamic converts it to a list type, so you can only select from values that exist.
There could be an issue connecting to the data source, or I've read about other issues where people used field caching and it was allowing bad values to be entered, or bugs that caused the error in older versions.
It would help them narrow it down if you specified the version and what client you're using when you get the error.
Either way, the "validation" for dynamic fields is just validating that the value exists in the assigned table so there's no other settings.
We think it is related to a timeout period, which might be shorter when saving the template compared with loading the field values.
The users were getting very long load times to load the lists, greater than 15 seconds. The lists were loading however, but when going to save the template the validation error would pop up.
Today we found that the lists were loading super fast, and saving was working. So it could be a timeout disguised as a validation error.