when it loaded, it said the DB had changed, and came back with dozens of:
CHANGED : (Field) fieldname->id - DbDefault (0 to )
and a few of these:
CHANGED : (Field) view->PolicyExceptions - NativeDataType (752 to 253), Attribute (36 to 32)
CHANGED : (Field) view->Name - NativeDataType (752 to 253), Attribute (36 to 32)
it looks like its mostly targeted to views and reports
In previous version some default values for integer field are set to 0 even there is no default value in database. It seems the change tries to fix it.
The attribute 36 changed to 32 means the field is not updatable. Maybe the field was wrongly detected as updatable in old version. Did the change fix it?
As for 752 to 253, I’m not sure what database type you are using. It seems it tries to fix detected data type.
If you think it has detected wrongly, you better report to support.
As explained, it only tries to detect the data type and default value more accurately, you’ll know if it is correct by comparing with your database scheman, whether or not the app can run does not matter.