From the Microsoft Dynamics 365 Business Central and NAV Blogs: Change measurement; Noisy problem; Extension; Data backups

• Change item base unit of measurement
• Dynamics 365 Business Central: Noisy problem in UsageCategory and ApplicationArea related to search
• Dynamics 365 Business Central: How to check if your extension is running on a trial tenant
• D365BC - data backups

Change item base unit of measurement

On his Dynamics NAV Essentials blog, Mahmoud AlSaadi stated that during a recent implementation of Microsoft Dynamics NAV 2018, a client wanted to upload the master data from the company's old legacy ERP system. In the old ERP system, there were two units of measurements: Each and piece.

Regardless of the terminology used to describe this unit, each term is just an identifier of one unit, he stated. The data import happened at the beginning of the year, and then the opening balances and transactions were posted to all the items throughout the whole year.

Now, at the year end closing, the client decided to clean their data after reaching a stability status, and for that purpose, they decided to link all items to the unit of measurement 'each,' rather than 'piece.'

So the result should be one unit of measurements "EA," and piece should be cleared from the system, according to AlSaadi. However, the change leads to an error message.

You can see what the error message is and how to resolve it here.

Dynamics 365 Business Central: Noisy problem in UsageCategory and ApplicationArea related to search

On the Stefano Demiliani Technical Blog, Demiliani stated that many AL developers have the same problem ...