From the Microsoft Dynamics 365 Finance and Supply Chain Management blogs: Mode-of-delivery trap; Apache Spark update; Electronic reporting; New/deprecated features

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

• The mode-of-delivery trap
• How to prepare for the Apache Spark update
• Electronic reporting: Importing configuration from Dataverse
• Looking ahead: New and deprecated features in 2025

D365 and the mode-of-delivery trap

Writing on his blog, Kurt Hatlevik stated that in D365 SCM, the "mode-of-delivery" field is important because it tells how goods are delivered to your customers or received from your vendors. 

However, he noted that if you use this field incorrectly, it can cause problems in other areas, such as eCommerce and finance, leading to a chain reaction of issues and expensive, avoidable fixes.

Hatlevik wrote that in D365 SCM, the mode of delivery identifies the method by which an order will be delivered. He then explained some of the most common misuses of the mode of delivery.

• Using the mode of delivery as a warehouse management system or route planning tool. 
• Storing unrelated carrier or service details.
• Overcomplicating the setup.

Finally, Hatlevik discussed the right way to implement the mode of delivery.

How to prepare for the Apache Spark update

On the Stoneridge Software blog, Kristofer Schlieper wrote that clients using Microsoft Dynamics 365 Finance and Operations connected to the Azure Synapse link for Dataverse will soon have to upgrade to Apache Spark 3.4.