You go back, Jack, do it again, wheels turnin' 'round and 'round
![]() |
Solomon and CRM Quantity issues. | ||
| There is some dissonance between Solomon and CRM when it comes to decimal precision. Solomon has greater decimal precision than Microsoft CRM. (In fact, Solomon supports $.000000001 nine point decimal accuracy.) So, during the calculations of Line item totals you may see the system go off by a penny. Then, on the total, the pennies might add up to equal $.01 for each line item. If you've watched the movie Office Space, you know that can add up to millions. Now first you have to ask yourself, "Why, after owning MBS apps like Solomon and Axapta, would someone make a bonehead decision like..... 'Nobody will ever need 5 decimal points'?" Well, decisions like that do happen. You may ask, "Who would ever do such a thing?" Obviously, someone at MSFT wasn't thinking straight. I have customers in the Chemical business. They sell tanker trucks, and ocean-going tanks of certain chemicals. Since it is distilled in water, they sell this material by weight. Chemicals are often brokered per kilogram; however, when selling this to the end customer, it may be converted to pounds or tons, depending on the customer's needs. So, when one sell in quantities of 40,000 pounds, you need to be able to convert the weight into metric and back. Poor rounding behavior could cost you a few hundred dollars per load. So the inability of CRM to manage this transition makes for a bit of fancy footwork on our part. In CRM 1.2, we were stuck with this behavior. In CRM 3.0, we are able to leverage the CRM SDK to our advantage. So how do we do it? We disable the field controls on the unit pricing and the calculation totals on the invoice and orders, through the supported ISV model, of course. Then we will round the numbers from Solomon so they fit into the CRM field appropriately on Quantity and extended price. However, with a bit of magic we are then able to suppress CRM from calculating the total for the Invoice. We are able to get the actual number from Solomon AR Doc for the Invoice totals and line item totals and add them on the CRM Invoice directly. This way we are able to get CRM to reflect the EXACT total — not what CRM would calculate the total to be based on inaccurate line item extended prices. | |||

Comments