From the Microsoft Dynamics 365 for Finance and Operations/AX Blogs: Units of measure; Lump sum; Custom workflows; Failing deployments

This week on the Microsoft Dynamics 365/AX blog roundup:

• Units of measure issue – Microsoft Dynamics AX 2012 R3
• Use the lump sum trade allowance agreement with care
• Dynamics 365 for Finance and Operations – things to consider when exporting data to BYOD
• Failing Dynamics 365 F&O deployments? Last resort workarounds

Units of measure issue – Microsoft Dynamics AX 2012 R3

On the Encore Business Solutions blog, Katalin Kegel stated that during a production project in Microsoft Dynamics AX 2012 R3, the company ran into an issue that's difficult to handle once it has occurred.

But if the business analyst or user knows about the problem, there is a hotfix that can solve the problem before it happens, she stated.

In a number of manufacturing environments, users can run into situations where the inventory unit of measure and the bill of material (BOM) unit of measure are different.

This really isn't an issue since users know how the unit conversions deal with this situation. They also understand how each Dynamics AX functionality uses the appropriate unit of measure by default, converting where necessary, Kegel stated.

However, there is a known bug in the R3 version where the reset status functionality is used on a production order and a cancellation picking list journal is automatically created.

You can read about it here.

Use the lump sum trade allowance agreement with care

On the D365Tour blog, Yohann Rolland stated that sale pricing can be set up in a number of ways in Microsoft Dynamics 365 Finance and Operations. It can be set up with the sale price ...