You’re offline. This is a read only version of the page.
Hello, everyone
I've encountered some bug (feature?) with my Dynamics CRM: there is a main form for some custom entity. That form contains a few required fields; 2 of those required are non editable (business logic - you can't create that entity instance manually, but can edit some of the fields). Despite of that setup I\ve been somehow able to create that record manually: long story short - form allows me to save the record without filling those 2 required non editable fields; when I leave some other required field empty though - system says that I suppose put something to it (to editable field), but once it filled - still allows me to save without filling non editable required ones.
Is that some bug or expected behavior?
PS: Using Unified Interface if that makes any difference
*This post is locked for comments
Hello,
This is the default behavior of the CRM since older versions and it was always like that.
The CRM will not check for the empty read-only fields even if they are required, and the user can save the form.
It is not a bug, bcz if the user cannot modify the fields, therefore, no validation should be done on them. Otherwise, if it is mandatory to verify them, you can add some JavaScript.
I can confirm this behavior not only on UCI but legacy (classic UI) as well.
I tried this on Account entity, I made Account Name filed read only and then tried to save record, which it did saved without filling data in that field.
Just to reconfirm I created new Filed from scratch and made it required and then made it read only on form, still CRM was able to save record both on Unified Interface and on classic UI as well.
#1
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
#2
Community Member
54
#3
Victor Onyebuchi
6
Share
Report
All responses (
Answers (
