Making mistakes is human. Some mistakes can be easily corrected; some will require additional attention. In this post, I share an option to correct the name of security objects created using the Security configuration options in Microsoft Dynamics 365 Finance and Operations.

Development versus configuration

As you might know, there are two options to extend or change the security in Microsoft Dynamics 365 Finance and Operations. One option is by development in Visual Studio. Using the development option, it is quite easy to extend or change the label of the security objects. There is another option to change security on the application level with help form configurations. When you have created new security objects with help of the configuration options, then there is no functional support to change the name of the role, duty or privilege. This post will not elaborate on all differences, options, pros and cons for using one of these methods.

When you use Dynamics 365 Human Resources, there is no development environment available. Then it is required to do all changes using the Security configuration form.

Why change the name?

There can be cases where you have a spell error, typo or the need to change the name of a role, duty or privilege. There is a quick way to duplicate the object and change the name, but this has some side effects. When you duplicate a role, you have to move the users from one role to the other; eventually also the organization assignments. If you have all users assigned manually, it can e a tedious job to move a lot of users with the correct organization assignments. Also, when there are workflows configured to assign users based on the role membership, it requires an action to change it.

When you duplicate a duty and you are using segregation of duties, you might need to add or change the rule set. If you forget to check this, you can introduce a risk in your organization.

Change the name of new configured security objects

In the video below, I will explain how you can change the name of security objects which have been created using the Security configuration form in Dynamics 365 Finance and Operations. The video explains it for security role names, but you can actually apply the same procedure for duty and privilege names.



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!

3 replies
  1. Calvin Eddings
    Calvin Eddings says:

    This is terrific tip, something i have wanted to do very often. Thank you for sharing. Question – is it time proven? Sometimes bugs come out over time.

    Reply
    • André Arnaud de Calavon
      André Arnaud de Calavon says:

      Hi Calvin,

      So far, I have used it myself several times before. Even two years back. I haven’t seen a side effect myself yet.
      If you have a customization which depends on a relation on the role name, there might be an issue. The out of the box features are not storing the name, but a record ID reference of a system table containing the role information.

      Reply

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published.

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