From the Microsoft Dynamics 365 Business Central blogs: Tri-state locking; Bound actions; Teaching tips; Telemetry set up

In this week’s Dynamics 365 Business Central blog roundup:

• SQL Server and read committed snapshot isolation impact
• Automate telemetry set up
• What are bound actions in Business Central APIs?
• How to disable or switch off teaching tips for all (selected) users at the same time – customization

Dynamics 365 Business Central: SQL Server and read committed snapshot isolation impact

Writing on his blog, Stefano Demiliani discussed the tri-state locking feature and the new read committed transaction isolation level in the latest release of Microsoft Dynamics 365 Business Central.

Demiliani noted that he has already written about this new transaction isolation level and how it helps to reduce locks. He pointed out that his friend Duilio Tacconi has also written a great post explaining the impact of enabling the tri-state locking feature on Dynamics 365 Business Central SaaS and on-premises.

But as Duilio explained, on SaaS you can just turn on the feature via feature management page, while on-premises you need to do something more: enabling read committed snapshot Isolation on SQL Server.

In his blog post, Demiliani offered some information that you need to remember to efficiently use the new locking feature for D365BC on-premises environments. He also answered the question: Should I enable RCSI on my Dynamics 365 Business Central on-premises installation?

What are bound actions in Business Central APIs

Writing on his blog, Alberto Soben pointed out that one of the best ways to integrate D365BC with other systems is through APIs, which enable you to trigger D365BC logic through bound actions.