Mapping for Data Types
[Rate this topic]

The following table describes the mapping for data types in a scenario where the data type for the variables are different:

change from

change to

result

explanation/processing

Character

Longer character

OK

 

Character

Shorter character

OK

 

Character

Number

 

Existing data may become non conformant

Character

Date

Error

Non-date fields cannot be mapped to date fields.

Date

Different date with more unknowns

 

(For example, mm/dd/ yyyy to mm/dd/ yyyy). Existing data can map to new specification as it will hold all required components.

Date

Different date with fewer unknowns

 

(For example, dd-/mm/ yyyy to dd/mm/ yyyy). Existing data containing UN that is no longer accepted will be deleted.

Date

Any other format

Error

Date fields cannot be mapped to non-date fields.

Date without unknowns

Different date without unknowns, same or higher precision

 

(For example, mm/dd/ yyyy to mm/dd/ yyyy hh: nn).  In Migration, contents of DATA will be remapped.

Date without unknowns

Different date without unknowns, lower precision

 

(For example, mm/dd/ yyyy to mm/dd/ yyyy hh: nn). May cause truncation, such as loss of time component.

Number

Higher precision number

OK

 

Number

Lower precision number

 

May cause truncation

Number

Shorter character

 

May cause truncation (For example, 6.2 to $5)

Number

Longer character

OK

 

Number

Date

Error

Non-date fields cannot be mapped to date fields.

 

 

Copyright © 2014 Medidata Solutions, Inc. All rights reserved.



How do you rate this topic?