Source Field Migration
When you upgrade from an earlier version of Composer to v7.10 or later, several field types in your existing sources are migrated and converted to supported field types. Composer no longer supports implicit field type conversions: when you change the field type for a field, you effectively create a new derived field. See Create and Modify Derived Fields.
Field Type Conversion: Previous Releases to Current Release
Scenario: You have a
date_year field defined as an integer in your original database.
Composer (previous releases):
date_yearis defined as a number or integer (dependent on your version).
You set the
typeas Time with Custom Pattern
Composer treats the field as a
Composer, on upgrade, will now have two fields for each affected field in your source.
date_year_original. The Label text is appended with
Original. The field type is set to
numberand the field is not visible (Visible toggle disabled in the Fields tab).
date_yearas in your original source. The Label text and other settings are unchanged. This is a derived field, using the expression
If you create a new data source that uses the
date_year integer from your source, you can create a derived field to change the
time, using the expression
Possible field type conversions and limitations performed on upgrade are listed in table below. This is not an all-inclusive list:
|Data Type conversion||Derived Field Expression||Requires Derived Field Support|
|ATTRIBUTE to NUMBER||Yes|
|ATTRIBUTE to TIME||Yes|
|NUMBER to TIME||No|
|NUMBER to ATTRIBUTE||Yes|
|TIME to NUMBER||Yes|