Notifications
Announcements
No record found.
Hi,
How can I delete table records from UAT environment? I don't have a menu item to delete records. So is there a way to do it?
You need to access dB of UAT, Then only you can delete the records from there.
If I delete records from UAT how can I sync UAT database again?
Also can I have access to Prod database and delete records from there?
You can not access Prod database. Only Microsoft can.
Hello,
The only way is to create the menu Item you do not currently have then you can delete records taking into consideration your validation.
Howerver, you can also use a runnable class develop from the DEV and deploy to both UAT and Prod.
Before you delete table records from an environment you need to do a validation if this function does not affect other tables and related data to avoid getting error message in the solution.
You can have access to UAT and DEV environment DB via LCS.
Example, On self service environment (e.g. UAT), You can order a access to DB as follows:
If you want to run a job in prod, an alternative can be to write a runnable class. Please check the following post for more info:
dynamics365musings.com/.../
Hi Alireza,
So I can run this runnable class in PROD or UAT by typing the url in the browser correct?
I have a code in UAT that will affect prod if I don't delete records from it first. But how can I merge this runnable class to Prod first if the code is already in UAT
As there is one date for PROD release only
community.dynamics.com/.../odbc-driver-17-for-sql-in-uat-environment
Hi IntegrationBeginner ,
Once you create a class i Dev, you need to create a deployable package in order to run this class i UAT and Prod.
This deployable package needed to be installed in one UAT environment first so you can activate it as release candiatae.
What to do in my case then. I don't want to affect PROD..can you look at the error I got in UAT in the url I shared in the previous reply. I want to know if it can be solved in UAT easily and make sure if I merge to PROD it won't break it.
We have 3 default environments by default for a D365FO implementation. And each of them have their purpose.
Anything you would want to do on Production as per customization should be initiated and tested on the development environment; moved to UAT.
Find a way to replicate the error on your dev. Get it resolved, create and apply a package on the UAT: This is the best practice on D365FO.
If the only way to delete those records is via a custom class, then I recomend you to use the new functionality "Run custom X++ scripts with zero downtime", it will allow you upload a custom class and execute it without deploying a new package in the environment, if you have worked with the previous versions (aka Axapta) it's something like executing a job in the production environment. The advantages are two, you don't need to stop the environment to upload the class, and once it is tested and validated in a uat environment (with a fresh copy of the production database, this is very important), then you can execute it in the production environment.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 664 Most Valuable Professional
André Arnaud de Cal... 522 Super User 2025 Season 2
Sohaib Cheema 303 User Group Leader
