You’re offline. This is a read only version of the page.
Announcements
Hi All,
Greetings.
I have a user from Maintenance department who have access to Maintenenace modules. I am developer in AX so I have System admin roles in AX.
Recently i did a change in one form in HR module in " TEST ENVIRONMENT".the form is customized where I did the changes
The maintenance user can access only few forms in HR module & the said form can be accessed by him .But what was surprising is that user cant see the changes made by me in that form.
Can someone possible highlight what would be reason behind this behaviour
Reagrds
You are awesome Sir
; Thanks
It worked by giving the admin roles and restarting the AX and clearing the usage data
Thanks
again
I assume you did AOS restart and x++ compile like suggested.
You didn't yet answer my question about the nr of AOS in your test system. If you have more than one, please follow the suggestion of my previous post.
Next steps:
- Is the user having Admin role or something else? If not, please add Admin role and test if they can now see the changes. If yes, you didn't take into account proper security in your development, or your user doesn't have proper security roles
- Did you ask your user to clear their usage data? If not, please do.
Please let us know if this helps.
As the system is more stable from last 5 years, the client has test and prod environment. We normally do any changes in test environment(the aos for test is different than prod)
Last time also i developed a report and the report was not seen by user. this report was total new developed from scratch in test. I moved it to Prod the new developed report but still user cant see. Ended up giving new roles, privileges etc and assigning that new role to user than user was able to see.
The case is different now as the form is already developed customized which user has access too. I made recent changes in the form but the changes are not visible to user in test. Any idea ? The user cant test the changes in test environment
How was the change deployed in the test environment? Or did you develop directly in test environment? Does the test environment have multiple AOS? If you develop in this system, that means that actually the system is a development system, not a test system. A dev system is less stable for users because of ongoing dev activities, so I recommend you use a dedicated development system to implement your changes.
When you bring code to your test system, you should have only one AOS running. After deployment, AOS restart, full x++ compile, CIL generation and db sync are needed. For just a form, x++ compile is enough, though. But you should have a proper deployment process in place to ensure that your system is in a consistent state after deployments.
In general you should follow Microsoft's guidelines when deploying customizations across environments: docs.microsoft.com/.../deploying-customizations-across-microsoft-dynamics-ax-2012-environments-white-paper
#1
André Arnaud de Cal...
293,406
Super User 2025 Season 1
#2
Martin Dráb
232,552
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (