From the Microsoft Dynamics 365 for Finance and Operations & AX Blogs: Locked dimension; Disabling TLS 1.0; Sales orders; Upgrades

This week on the Dynamics 365 for Finance and Operations and Dynamics AX blog roundup:

• The secret of locked dimension when using reservation in D365FO
• Disabling TLS 1.0 and the impact on Dynamics AX 2012
• Sales orders stuck on hold in Dynamics 365 for Finance and Operations
• Ensuring a seamless Dynamics AX 2012 R3 upgrade using upgrade analysis functionality

The secret of locked dimension when using reservation in MSDyn365FO

On his Un tour d'horizon sur (An overview of) Dynamics 365 blog, Yohann Rolland stated that when you use the reservation functionality on sales orders in some contexts, you want to ensure the reservation that has been done (on a batch number for instance) won't be removed.

In simple stock management contexts, there are some locking options that aren't obvious at first if you want to use locked dimensions. So Rolland decided he should blog about them.

First thing to know: it applies only when there is no on hand available stock. If there is some, and the reservation is setup to be automatic, the reservation will be done instantly just after the sales order line is saved, and the locking functionality does not interfere here.

When a purchase order is created for a specific customer need, for example, through marking, the locking functionality makes sense.

You can read more about the locking functionality here.

Disabling TLS 1.0 and the impact on Dynamics AX 2012

On the Microsoft Dynamics AX 2012 Administration Tips & Guides, Boris Diroo stated that if you haven't disabled TLS 1.0 yet, you're not PCI compliant. As of June 2018, TLS 1.0 is ...