From the Microsoft Dynamics 365 Finance and Supply Chain Management blogs: Code upgrade conflicts; Clean up jobs; Financial reporting; Invoice capture

In this review of the Microsoft Dynamics 365 Finance and Supply Chain Management blogs:

• Detection of code upgrade conflicts
• Clean up jobs
• Unlocking automation efficiency with invoice capture
• Enhancing and streamlining financial reporting

Detection of code upgrade conflicts

On his blog, Martin Dráb wrote that when you customized an element, such as a method or form, in Dynamics AX, a copy of it was saved in a new layer above the original. 

He stated that this created two versions: the unmodified one in a base layer, e.g., SYS, and your customized version in a higher layer, e.g., CUS. Dráb pointed out that if Microsoft updates the original element, your customized copy will hide those updates unless you update your code to match, which is often a challenging task.

He noted that with Dynamics 365 Finance and Operations, overlayering isn’t allowed, so your customizations can't hide Microsoft's standard code. 

Dráb wrote that now when Microsoft releases an update, your extensions are applied and everything is OK, and the difficult and expensive code upgrade process isn’t needed anymore – almost.

However, he stated that there can still be changes that affect your customizations. For instance, if you've added custom features to the sales order header V2 and Microsoft releases a V3 version, you'll need to add your customizations to the new version as well, he noted.

In his blog post, Dráb explained the process of detecting code upgrade conflicts.

Clean up jobs in D365 F&O

On her blog, Anitha Eswaran wrote that you should always remove old and unused data to improve the performance of your system.