1
In several places in the UI, EDT is enforced so that data is consist. Unfortunately we found out that in some cases the data that flows thru the DM, this data is not bound by that EDT. This means that values that can not been seen in the UI are being brought into the table. Once example is the saleprice (unit price) is only decimal places, so 12.56 is seen, however, if it is brought in via DM, it could be 12.569, but only 12.56 is seen on the UI. This also leads to issues downstream.

My strong suggestion is to enforce the same rules on the DM import as we have are bound in the UI.
Category: Data Management
STATUS DETAILS
Under Review
Ideas Administrator

Thanks for the ask. We are in the process of reviewing.