Dynamics Business Central / NAV Developer Digest - Vol. 526
ArcherPoint’s Developer Digest focuses on Microsoft Dynamics 365 Business Central and Dynamics NAV development. This week’s volume includes checking the health of Microsoft services for multiple tenants, speeding up sync from BC to Dataverse, and making sure obsolete keys stay obsolete.
The Dynamics 365 Business Central community, consisting of developers, project managers, and consultants, collaborates across various platforms to share valuable insights. At ArcherPoint, we greatly value their dedication and expertise. To ensure widespread access to this technical knowledge, we created Developer Digest.
For partners: checking the health of Microsoft services for multiple tenants
Users can check on the health of their Microsoft services using the Microsoft 365 admin center.
From Microsoft:
“You can view the health of your Microsoft services, including Office on the web, Microsoft Teams, Exchange Online, and Microsoft Dynamics 365 on the Service health page in the Microsoft 365 admin center. If you’re experiencing problems with a cloud service, you can check the service health to determine whether this is a known issue with a resolution in progress before you call support or spend time troubleshooting.”
While this works for individual users, partners might have some difficulty seeing the health of individual tenants using their CSP account.
Waldo addresses this problem and offers tips and additional resources in his blog, Troubleshooting Series – Ep1 – Admin Center – Service Health.
Speeding up the sync from BC to Dataverse
When integrating Business Central with Dataverse, the initial synchronization can be very slow depending on the number of columns and records are in a table.
Bert Verbeek tackled this issue recently and offered two alternatives: perform a manual sync or import through Excel. Each can significantly cut the synchronization time, but of course, there are gotchas you need to be aware of.
Check out his blog, Performance of the initial load to Dataverse from Business Central, to learn more.
Making sure obsolete keys stay obsolete
At first glance, deprecating an SQL index or making it obsolete should remove it from use in an extension. However, that’s not what happens, and this can cause delays or even deadlocks. There are some additional steps required before the index is truly removed from use.
Duilio Tacconi explains this problem and offers a simple fix in his blog, Obsoleting Keys: things to know.
Are you interested in Dynamics NAV and Business Central development? Check out our collection of NAV/BC Development Blogs.
Read “How To” blogs from ArcherPoint for practical advice on using Microsoft Dynamics NAV and Dynamics 365 Business Central.