“Units of Measure”

UOM was a very problematic issue for our integration. This is because the business logic is so different between Microsoft Solomon and MSCRM.

It does not make sense that MSCRM has such a strict UOM system when the conversion is not used on orders. Is there any way to manipulate these required data points when they are not going to be used during the integration for any reason?

Our Response:

The requirements of the Microsoft CRM pricing system, specifically involving the unit of measure, are more rigorous and less flexible than what is currently available in Solomon. We expect that the disparity between the two systems will also pose problems during future implementations.

While you can change required level of fields on some of the Microsoft CRM forms, you cannot change the required level of system required fields, nor is it possible to change the underlying functionality of the Microsoft CRM pricing engine. Therefore, please enter a product suggestion on CustomerSource, outlining the specific manipulations you want to make to the existing structure.