From the Microsoft Dynamics 365 Business Central blogs: TryFunction; Send notifications to Teams; GL budget entries; File size limit

This week on the Dynamics 365 Business Central blog roundup:

• Dynamics 365 Business Central and TryFunctions: be careful
• Send Business Central environment notifications to Teams
• Expert tips for importing and exporting GL budget entries in Business Central
• Business Central on-premises and max upload file size limit

Dynamics 365 Business Central and TryFunctions: be careful

On his blog, Stefano Demiliani noted that most people know what try methods are in Dynamics 365 Business Central and Dynamics NAV. Try methods in the AL programming language let users handle errors that occur in the application during code execution.

Demiliani pointed out that the official documentation about TryFunctions says:

[B]ecause changes made to the database by a try method aren’t rolled back, you shouldn’t include database write transactions within a try method. By default, the Business Central Server configuration prevents you from doing this. If a try method contains a database write transaction, a runtime error occurs.

He stated that generally, you don’t need to perform write transactions inside a TryFunction (for transaction consistency) and in the past, particularly with D365BC on premises, you'd most likely get an error message if you did that.

Demiliani then explained why you should avoid doing write transactions in a TryFunction on Business Central SaaS, saying that there's an inconsistency of behavior between on-premises and SaaS that can cause serious problems if TryFunctions are not correctly used.

Send Business Central environment notifications to Teams

Writing on his Business Central Musings blog, Silviu Virlan pointed out that most professionals working with D365BC online receive notifications of environment changes via email. However, he pointed out that it's possible to receive D365BC environment notifications in your Teams app.