You’re offline. This is a read only version of the page.
Skip to main content
Dynamics 365 Community
Cancel
Get involved
Get answers
Discover events
Learn Dynamics 365
More
Search
Community site session details
Session Id :
Copy
Close
Dynamics 365 Community Calls Return
Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft
Responsible AI policies for the Community
Dynamics 365 Community
/
Blogs
/
D365 Finance and Operations Technical
/
Post-PROD DB Restoration Steps
Post-PROD DB Restoration Steps
Views (4)
Manikanda_Gopal
22
Follow
Like
(
0
)
Share
Report
Hi Everyone,
While many resources explain the process of performing a point-in-time restore from Production to Sandbox in Dynamics 365 Finance and Operations, post-restore steps are often overlooked. This guide outlines essential actions to take after a successful database restoration.
Steps:
Verify Data Integrity
: Open a frequently used form to ensure that the latest PROD data has been copied to your UAT environment.
Enable User Accounts
: After a restore, user accounts might be disabled. Navigate to the System Admin module, go to the Users form, and enable the necessary user ID’s.
Import Missing Users and assign the role
:
Identify the list of users who require access to the UAT environment. Import these users and assign their corresponding roles. You can refer to my blog on importing multiple users and assigning the same roles to them.
Dynamics 365 Finance and Operations Technical Tips and Tricks: How to Assign the Same Security Role to Multiple Users in Dynamics 365 Finance and Operations(D365 F&O) (d365fandotech.blogspot.com)
Enable workflow batch jobs
: If you have configured any workflows within your system, enable the following four workflow batch jobs. Ensure that the status of each batch job is set to "Waiting" instead of "Withhold".
Email batch job:
Enable the email distributions batch job if required.
Custom alerts:
If the custom alters are configured in the production environment, disable it.
Email parameters:
Remove the email parameter setting that currently points to the PROD environment and change it to point to the UAT.
This step is necessary if your system has integrated with third-party applications and may not be applicable to all users.
Microsoft Entra ID:
Change the Microsoft Entra ID application ID that points to the production environment to the UAT application ID.
Azure Key Vault parameters:
Remove the secrets, delete the key vault setups, and reconfigure them with the UAT values.
BYOD
: Ensure that your BYOD data source is configured to point to the UAT instead of the PROD. Replace the PROD application ID with UAT in recurring integration data projects(DMF). Set the recurring integrations batch job to "Waiting" status from "Withhold".
Endpoints
: Configure the business event endpoints if it's required.
Export backup:
Once all the above steps are completed, export a database backup from the UAT environment. This backup can be used to restore the latest database to development machines.
This was originally posted on '
https://d365fandotech.blogspot.com/2024/08/prod-db-restore-into-uat-environments.html
'
Comments
Add new comment
Comment on this blog post
New#123
You don't have the appropriate permissions.
Messages
Welcome,
Profile
Messages
My activity
Sign out