Hi Subhash,
When mapping to destination fields that represent physical measurements (measurement fields and numeric attributes), the units of measure in the source data may be: (1) missing entirely, such as when all the values in a source field have the same implicit unit; (2) inconsistent, such as when different text strings are used to represent the same physical unit (e.g. inches, inch, in, or u2018"u2019); or (3) different for each source data value.
For Eg :
Case 1:
Source
WIDTH (INCHES)
3
2
1
2
Now in this case the measurement values have the same implicit unit (which is missing) and we can see the numeric values.
Case 2 :
Source:
SOCKET SIZE
2 u201C; 2.5 INCH
10 milimtres; 12 mm
15mm ; 20 millimeters
Here is the case where we have multiple delimeted values with different measurement units and Inconsistent unit strings.
Case 3 :
Source:
WIDTH WIDTH (UNIT)]
3 inches
2 u201C
1 inch
2 1/2 IN
Now here numeric value is stored in a pair of fields, one containing the numeric value and the other containing the corresponding unit of measure string.
In each of these cases, unit of measure strings are automatically normalized and appended to each numeric source data value based on the physical dimension of the destination measurement field or numeric attribute to which the source field is mapped. If necessary, each numeric measurement value can be converted to a target unit, or
manually edited to override errors or omissions in the source data.
MDMu2019s measurement data type guarantees unit of measure consistency and permits each individual measurement
value to have its own distinct unit. Moreover, unit of measure strings are automatically normalized against MDMu2019s built-in dictionary.
Hope this would help!!!!!
If helpful do reward points!!!!!!!!1
Regards,
Parul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.