55

Currently, when database restore is finished visa DSE team, by default only "admin" user is enabled. After this, admin user needs to remove any environment specific data and enable all the users manually.


 


It would be helpful if LCS gives the ability to select a runnable class or database script to be executed automatically after database refresh. This will make the whole database refresh approach automated and easier to maintain. 

STATUS DETAILS
Under Review
Ideas Administrator

Thank you for your feedback.

This is a great suggestion! We will consider this in our roadmap.

Sincerely,

Manali Dongre

Microsoft.

Comments

M

Indeed, it would be very convenient to automatically anonymize or scramble the data after a database refresh. The automated scripts would prevent human error (like someone forget to run the scripts).

Category: Lifecycle Services

M

Our implementation has 18 entities with 220+ user accounts... after activating 220 accounts due to data refresh you'll know that something is missing.

Please, add functionality to easy this cumbersome operation.

Category: Lifecycle Services

M

Especially our customers that fully utilize the Human Resources module and store sensitive data within the ERP (such as payroll and SSN information) have requested automated data scrambling or automated database manipulation scripts for a PROD copy to TEST. Customers do not want their IT administration teams to be able to access this type of information.

Therefore, it would be very helpful to be able to utilize automated scripts when running the self-service database refresh.

Category: Lifecycle Services

M

It would be very helpful to be able to upload scripts that would automatically run when the self-service database refresh happens in an environment. Some customers have requirements to purge or manipulate other data in the environment other than what MS does by default.

Category: Lifecycle Services

M

I have an extensive script to reset many things in our test enviroment after a refresh. With news of a "hardening" of the test environment so that users will not be able access the database, I don't know how I will be able to execute my script.

Category: Lifecycle Services