Within Dynamics 365 fields can be set as business required, which helps to ensure these fields need to be populated for the record to be saved. Fields can also be set as read-only, preventing Users from entering data manually. Prior to v9, the business required validation was always enforced, even if the field had been made read-only. With Dynamics 365 v9 (v126.96.36.1994 at the time of writing this blog) this is no longer the case. The screenshots in this blog will be used to show an example of this in Dynamics 365 v9.
The screenshot above shows a Contact record being created where the Full Name and Job Title fields are business required. The Job Title field has been set to read-only on the form in this case. After entering a Full Name and hitting save, the record is created without any issues as shown in the screenshot below.
This isn’t limited to creating new records but can also occur while attempting to update existing records.