Hiding Data in Test Environment

(0) Share

Report

Posted on by Mazherullah

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 have the same question (0)

All responses (13)

Answers (0)

Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

I do not see a question on your post. If the question is that if it is possible, then the answer is yes, you can create custom security roles or XDS policy to hide sensitive information. You just have to make sure that there are no loopholes, you need to have strict control on who has access to the SQL Database, or have Administrative privileges within AX.

Was this reply helpful? Yes No
Suggested answer

Solozmar 796 on at

Like (1)

Report

Another approach I might suggest (though won't work if you require that data), is to scramble that data, or remove it. For example, on all copydowns from Production down (TEST, UAT, DEV, etc.) we update the HCM/human resources and payroll table values to 0, 1234, NULL or similar. That way we are not worrying about additional permission changes or altering functionality.

Was this reply helpful? Yes No
Santosh Yadav 420 on at

Like (0)

Report

why don't you create few security artifacts (new privileges, duties, roles etc.) around this and pull over all the required menu items those you don't want to expose to *some* users. only thing you need to be cautioned is, these security artifacts don't need to be promoted to other env (as they don't needed), these are just needed for your data protection.

deleting the data is absolutely not recommended approach as financial entries having so many references across the tables.

Was this reply helpful? Yes No
Ahmad wali 105 on at

Like (0)

Report

I think you wanted to raise a point over here. You can apply the security role level on it.

Thanks

Was this reply helpful? Yes No
add on at

Like (0)

Report

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.

Was this reply helpful? Yes No
migi111 485 on at

Like (0)

Report

Hi,

I have exactly similar situation and need to scramble HCM data. Can you describe your solution a little bit?

Was this reply helpful? Yes No
migi111 485 on at

Like (0)

Report

....and my response was for Solomon Maricle's reply.

Was this reply helpful? Yes No
Ahmad wali 105 on at

Like (0)

Report

Hi,

Do you want need the scrambling script?

Thanks

Was this reply helpful? Yes No
Mazherullah 345 on at

Like (0)

Report

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

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

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).

Was this reply helpful? Yes No