How mandatory is required?

Microsoft recently released Dynamics 365 for Finance and Operations: version 10.0.11. In this release, there is a new preview feature where you can configure fields to be mandatory. I have tested the feature which is working for specific use cases. In a video, you can see a demo of how this feature works. There are some caveats that will be explained in this post also.

Designate fields as mandatory

From the 2020 Release wave 1 plan or Finance and Operations and also What’s new documentation, you can find the details for this new feature. When you have installed version 10.0.11 or today the PEAP for 10.0.12, you can enable the preview using the Feature management workspace.

(Update: As of October 2021, the feature is on by default.)

Initially, I was quite curious about what Microsoft offered as a solution here. Having the option to make fields mandatory without the need for a developer, testing, and deployment is for sure something positive for system administrators. I tested the feature and think it for sure adds value, but there are also downsides that you should be aware of. I have recorded a video with a demo of this feature and the cautions.


As you can learn from the video, you can use a new personalization option to enable fields to be mandatory. Some things to keep in mind:

  • The personalization is user-specific. It needs to be applied to all users via a push of personalization or users need to designate the fields as required themselves.
  • The personalization is also form-specific. Every form where you can manage the same field should be personalized.
  • A user has the option to (temporarily) disable the mandatory requirement.
  • The option does not support all fields. As an example, the extensible control used for financial dimensions is not supported.
  • When using Saved Views, a user can simply change the view to a view where the field is not mandatory.
  • There is no condition option. It is always mandatory when the Required option is enabled.
  • When using data import or Open in Excel, the field is not marked as mandatory as it is a form personalization only.

When you want to really ensure a field will be mandatory for all users, you must go for a customization. Here you have the option to control the requirement on table level which will then be enforced throughout the system on all forms and for all users.

The feature will be more valuable for Dynamics 365 Human Resources where it is not possible to install deployable packages with customizations.

I do hope you liked this post and will add value for you in your daily work as a professional. If you have related questions or feedback, don’t hesitate to use the Comment feature below.

That’s all for now. Till next time!

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.