Mapping External Source Fields to SBM Fields

Many field mapping options and settings vary depending on the type of database you are importing from. For details on mapping fields for specific database types, refer to:

Mapping External Source Fields to SBM Fields

Mapping SBM Source Fields to Destination Fields

The following information applies to field mapping from all source database types:

• Values in the source field mapped to the receiving State field are added to the SBM State field. In addition, a state is added to the workflow assigned to the project items are imported into for each source State field value. You must manually link these states to transitions in your workflow in SBM Composer. You can manually map State field values; for details, refer to Mapping State Field Values.

• Most SBM fields can be mapped to; exceptions are the Project field, primary Multi-Relational and primary Single Relational fields, Folder fields, Sub-Relational fields, the system-provided Last Incident field, and deleted fields.

• You cannot map to the Project field. For data imported from SBM databases, the selections on the Specify Destination dialog box determine into which projects items are imported. For details, refer to Specifying a Destination for Imports From SBM Databases.

• SBM states use the Active/Inactive field to automatically determine the status of items in each state. You can map the Active/Inactive field to an SBM field, but it may be more beneficial to use SBM automatic setting of the Active/Inactive field.

• If you do not map the SBM Close Date field, the Active/Inactive status is used for imported items and the close date may be established as the date closed or inactive items were imported. If you map the close date field, source data is used to populate the Close Date field for imported items.

• When you map to auxiliary Single Relational and auxiliary Multi-Relational fields, records that do not already exist in the receiving database are added. However, only the system Title field is populated for these records. You can fully populate these records by performing a separate import of data from the related auxiliary table.

  Note: The value mapped to the Title field will remain the constant value in the display for all relational items created via the data import, regardless of how the Value Display Format for the table is set.

• Most source field types can be mapped to any SBM field type, and source field values are added to the receiving field based on its field type. For example, if you map a Single-Relational Companies field to a Single Selection field in the receiving database, Company records are added as disabled selection values in the Single Selection field.

• The wizard does not allow incompatible field types to be mapped. The following table describes the ODBC SQL field types that can be mapped to each SBM field type.

  SBM Field Type	Compatible ODBC SQL Field Type
  Binary/Trinary	Any of the following field types: SQL_CHAR SQL_VARCHAR SQL_SMALLINT SQL_INTEGER SQL_TINYINT SQL_BIGINT Zero (0) is interpreted as cleared; 1 is interpreted as selected.
  Date/Time	Depending on source field type, several steps of conversion may take place: SQL_CHAR SQL_VARCHAR SQL_SMALLINT SQL_INTEGER SQL_TINYINT SQL_BIGINT SQL_DATE SQL_TIME SQL_TIMESTAMP SQL_TYPE_DATE SQL_TYPE_TIME SQL_TYPE_TIMESTAMP
  Text	SQL_LONGVARCHAR - Can only be mapped to various Memo field types; truncation may occur. SQL_CHAR – Truncation may occur SQL_VARCHAR – Truncation may occur The following field types are converted to meaningful text representations: SQL_DECIMAL SQL_NUMERIC SQL_SMALLINT SQL_INTEGER SQL_REAL SQL_FLOAT SQL_DOUBLE SQL_TINYINT SQL_BIGINT SQL_DATE SQL_TIME SQL_TIMESTAMP SQL_TYPE_DATE SQL_TYPE_TIME SQL_TYPE_TIMESTAMP
  Numeric	The following field types are converted if they are in a meaningful textual representation: SQL_CHAR SQL_VARCHAR The following field types are only allowed for floating-point Numeric field types: SQL_DECIMAL SQL_NUMERIC SQL_REAL SQL_FLOAT SQL_DOUBLE The following field types are only allowed for Numeric fields in integral format: SQL_SMALLINT SQL_INTEGER SQL_TINYINT SQL_BIGINT
  User, Multi-User, Multi-Group, Single Selection, Multi-Selection, Single Relational, Multi-Relational	The following field types are converted using matching system title or login value (for user-type fields): SQL_CHAR SQL_VARCHAR When you import from generic ODBD databases, the following field types require augmenting information to textual foreign key values: SQL_SMALLINT SQL_INTEGER SQL_TINYINT SQL_BIGINT the following field types are only allowed for Multi-User, Multi-Group, Multi-Selection, and Multi-Relational field data imported from other SBM databases: SQL_LONGVARCHAR