From the Microsoft Dynamics 365 Finance and Operations Blogs: Batch jobs; Copilot & implementation portal; Microsoft Dev Box; Sysadmin role assignments

In this week’s Dynamics 365 Finance and Operations blog roundup:

• Add logging to sysadmin role assignments in D365FO
• Avoiding deadlocks and lost records when using batch jobs
• Copilot in Dynamics 365 implementation portal
• Microsoft Dev Box and D365FO local development

Add logging to sysadmin role assignments in D365FO

Writing on his Dynamics 365 Finance and Operations blog, Alex Meyer followed up a previous post about being able to grant or revoke the sysadmin role for testing purposes.

He noted that one of the things he pointed out was that before implementing this solution there needed to be a logging functionality to audit when a user was granted or revoked this access.

In this blog post, Meyer explained how he added this functionality. He wrote about the design, saying the first thing he had to do was to create a table to store when a user was assigned or revoked the sysadmin role. He then offered more information about how to add this functionality, how to test the solution, and how to report on the logged data.

Finally, Meyer stated:

After getting to this point, and having some discussions with other MVPs I think it would probably be best to get this solution on GitHub and open it up to the community. Be on the lookout in the upcoming weeks as I transition this over to being a public GitHub project.

Avoiding deadlocks and lost records when using batch jobs in D365FO

On the Docentric blog, Nenad Krantic wrote that batch jobs are a major part of Dynamics 365 Finance and Operations and a great way to asynchronously process large amounts of data. However, Krantic noted that if you're writing a batch job process that's going to use multiple batch jobs simultaneously on the same data, you should be aware of certain potential problems.

In his blog post, Krantic discussed how to solve the problem of deadlocks and so-called lost records by using just three fields and a couple of system methods. Krantic first explained exactly what deadlocks are and how to prevent them in D365 F&O. He also offered information about lost records and how to prevent them.

Copilot in Dynamics 365 implementation portal