This new feature in v5.12:

After a database sync, the entity field’s IsReadOnly flag is now properly synced with the target field’s requirement for an insert value, if the entity field’s IsReadOnly flag hasn’t been manually changed by the user.

In 5.12.1 hotfix appears to be working incorrectly because no matter how many times I manually set to readonly I keep getting "TargetPerEntityHierarchy" issues on every database sync.

How to I force it to read-only so the designer stops breaking but still allow me to properly perform database syncs? Currently due to new feature development I am running database syncs multiple times a day and this is slowing me down quite a bit (more from frustration than reality).

This is the error I get (once per instance which is around 10 or so):

The entity definition 'X' is in an inheritance hierarchy of type 'TargetPerEntityHierarchy' with the discriminator field 'Y' however the discriminator field isn't marked as read-only, which is required.

We'll look into it!

Reproduced

Fixed in new hotfix build 5.12.1 which is now available, which should fix your issue (manually marked readonly fields should now properly stay readonly)

Please next time, no need to get frustrated if something doesn't work, just report it and we'll look into it

Thanks. I avoid reporting things that aren't a bug and it took a fair bit to decide to lookup the release notes and notice that it explicitly called out my case. Actually it took several days of re-reading the note in order to believe that my case was suppose to explicitly work. I figured I was missing some database thing.

I will note that 5.12.1 hotfix is opening the 5.11 readme/release notes after it finishes installing.

TazMizZaz wrote:

I will note that 5.12.1 hotfix is opening the 5.11 readme/release notes after it finishes installing.

Thanks for this, I see we didn't update the readme file in the 5.12 branch. Will update that!