web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Synchronizing Role, Duties and Privileges Between Multiple Instances

(0) ShareShare
ReportReport
Posted on by 320

Hello:

We have three instances of Dynamics AX 2012 R2 CU6:  Production, Development and Sandbox.  Sometimes the roles, duties and privileges get modified in Production (emergencies) but not in Development.  This leads to issues if we try to modify Development and roll it into production if the starting points for both are not the same.

Is there a way that I can create an exact copy of a role from Prod and put it into development, make the changes in Dev, and then roll it back to Prod?  We currently export packages of roles.  But here's the issue?  Let's say that we had to modify the "Accounts Payable" role in production by adding a Duty and removing a permission.  This leads to two questions:

(1) If I just package up the Production "Accounts Payable" role, will my changes to the Duty and privilege also be bundled into that package, or do I have to export the duty and privilege also as part of that package.

(2) When the production package is applied to Development, will it make an exact copy, including any deletes?

If you could point me to a technical resource on how this works, that would be a bonus.

Thanks,

Rich Locus

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    237,795 Most Valuable Professional on at

    Security elements are saved to AOT as normal code and metadata (such as types, tables and classes) and use the same concepts. For example, you have layers - the usual approach is developing in a lower layer (e.g. VAR or CUS) and doing changes in Production (if necessary) in USR layer.

    It's then completely clear which changes were done in Production. Exporting changes means exporting the right model. Deleting changes means dropping the model.

    The exported model is an exact copy, nevertheless it's not sure that lower layers (e.g. CUS) in Development are the same as in Production - somebody may have done changes in Dev. You have to merge changes in such a case.

  • richlocus Profile Picture
    320 on at

    Martin:

    Thanks for responding.  I am fairly  new at this so I don't completely understand your response.  Since several people modify the Production AOT directly using the CTRL-D function, I need a way to push Production's AOT back on top of Development and Sandbox.  Do you have any suggestions?

  • Verified answer
    Martin Dráb Profile Picture
    237,795 Most Valuable Professional on at

    See Deploying Customizations Across Microsoft Dynamics AX 2012 Environments; it explains many concepts you need to understand.

    Also think again whether you really want several people with administrator permissions in your production environment. It's very dangerous.  

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans