You’re offline. This is a read only version of the page.
345
Dear All,
Usually I maintain the same setup/version in Production and Test Environment by frequent Backup of Prod. and Restore in Test.
But now my superior wants me to act upon differently.
He don't want to reflect the data in Test same as on Live. Reason, when some users give access to Test they don't want to see the confidential data like financial profit & loss data, payroll details of other users.
Instead of deleting the data on Test. I would prefer doing thru security role level.
Anyway for this.
AX version : AX 2012 R3 CU10
regards
*This post is locked for comments
I am not sure why this question arises.
If someone has access rights in live, and live is the same as test, then they can see the same data in both systems and don't need to go to test to view the data.
If you are going to test, then it should be done with the appropriate access rights, or it may not work in live.
If you want to test a process across several roles then the person with a level of expertise probably already has those rights in live. Obfuscating data would probably prevent such cross module tests being of any use.
So the important thing seems to be to ensure that you have the correct access rights in live, and that you do not give testers any different rights than they would have in live.
We have an X++ job in place that we run each time we clone our Production SQL database over our Quality Assurance and Test environments. You may write an X++ job which obfuscates or cleans your data, and put it as a mandatory for your system administrator who is doing the cloning to run it as part of your clone procedure (preferably in an automated fashion, like a PowerShell script or T-SQL job).
Hi migi111,
Reg. masking the HCM data, I think major data is payroll related details...that we can mask the basic salary with some standard amount.
regards
Hi,
Do you want need the scrambling script?
Thanks
Hi Mazherullah,
I would make two (or more) test environments. One I would use only for new employees testing, training etc. I would restrict access through security or transform sensitive data or both. This environment I would refresh very rarely. And the other environment/s I would refresh as needed for DEVs or sys admins testing etc.
I think you wanted to raise a point over here. You can apply the security role level on it.
Thanks
#1
Mohamed Amine Mahmoudi
100
Super User 2025 Season 1
#2
Community Member
48
#3
Zain Mehmood
6
Moderator
Share
Report
All responses (
Answers (
