Announcements
No record found.
*This post is locked for comments
Does it mean that they wouldn't be able to import changes, but they would be able to make the same changes by hand or paste them to code editor? What's the point of that?
If you want to stop them from making changes, disabling imports isn't enough.
I do agree with Martin. May be your issue is related to managing and tracking developments. A source control system such VSTS can be a good choice in such cases.
You cannot revoke specific rights in the developer workspace of AX, without going into very low level hacking through the Windows API handlers. A system administrator is a system administrator, and can do whatever they want to.
You can only avoid accidental code changes if you enable a Version Control System such as Team Foundation Server (TFS), and there if you revoke check-out/check-in rights from individual users, theoretically they will not be able to modify anything in AX.
There are ways around like they could disable VCS in the Version Control Parameters, so that is also not 100% guarantee.
The only correct approach is: remove System administrator rights from users, who are not supposed to do AOT changes, simple as that.
Also you could introduce some logic on SysImportDialog form to exit if it is not executed by specific users, but that could break other functionality of AX.
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.
Congratulations to our 2026 Super Stars!
Thanks to all of our 2025 Community Spotlight stars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Joris dG 5
Alexey Lekanov 2
Henrik Nordlöf 2 User Group Leader
