From the Microsoft Dynamics 365 Business Central blogs: Record changes; Data mirroring to Fabric; Release plans; Product environment access

In this week's Microsoft Dynamics 365 Business Central blogs:

• Record.IsDirty in Business Central 29: a worked example 
• Data mirroring to Microsoft Fabric announced
• BC release plans are going away. Where do you look now?
• Managing access to the production environment online

Record.IsDirty in Business Central 29: a worked example

Writing on his blog, Mohana Yadav stated that Business Central 29 adds IsDirty to the record API. 

He noted that it lets your AL code check whether a record has changed since it was loaded. This can help you avoid saving a record when nothing has changed and means you don't have to keep track of those changes yourself.

Yadav wrote that Record.IsDirty() checks whether a record has changed since it was loaded from the database. It returns true if any of the values in the record have changed and false if everything is still the same.

He noted that it gives you a simple way to check whether a record needs to be validated or saved, or whether the user should be prompted about changes.

According to Yadav, if you've used RecordRef.IsDirty(), the idea is the same. That feature has been available since runtime 5.0. Microsoft Dynamics 365 Business Central 29 now brings it to the record data type, so you can check for changes directly on the record you're already working with.

In his post, Yadav explained how IsDirty works on a customer card and how you might use it in your own code.

Data mirroring to Microsoft Fabric announced

Writing on his blog, Stefano Demiliani stated that Microsoft recently announced data mirroring for D365BC in Microsoft Fabric. This is a major development for companies that use D365BC data for business intelligence and reporting.