Service Now has many data types. Many of these are simple to understand with regard to migrating data and are represented in the target database table unchanged. There are some however where a degree of transformation takes place.
Source and Display Values
For some data types, ServiceNow supports retrieval of the display value of a fields as well as the underlying value that is stored. The table below identifies the field types that have a display value that can be retrieved and migrated to the archive. For more information regarding how to configure retrieval of display values in a project, see Enabling Retrieval of Display Values
Currency & Price
As part of retrieval, Precision Bridge looks up the currency code for the value.
A simple mapping to a string will give a currency in the form <decimal><space><code> e.g. 29.99 EUR. If mapped to a numeric field, just the number is stored. The currency code can be extracted using an assignment mapping with the function GET_CURRENCY_CODE
If the 'Generate Archive Targets' wizard was used to create the table and mapping, the amount and currency code will be stored in two separate columns in the archive table.
Durations - Prior to Release 6.0:
The value is stored in ServiceNow as a date/time, seconds since 1970-01-01 00:00:00. Precision Bridge convert this during transform to a string with format <days> <hours>:<minutes>:<seconds> If mapped to a string, this format will be displayed. If mapped to a numeric target, the value will be the seconds since 1970-01-01 00:00:00.
Durations - From 6.1 onward:
From 6.1 onward, durations are retrieved as a date/time, seconds since 1970-01-01 00:00:00. To support legacy projects and archive databases, two assignment functions DATETIME_TO_SN_DURATION_STR and SN_DURATION_STR_TO_DATETIME which will convert between the date/time value of a duration and the string with format <days> <hours>:<minutes>:<seconds>
Upgrade Note that if you are upgrading from Precision Bridge 6.0 to 6.1 and wish to continue to migrate duration values using the format <days> <hours>:<minutes>:<seconds> you will need to change your project to make use of the DATETIME_TO_SN_DURATION_STR function for duration fields. If you do not do this, the migration will work correctly, but the duration value will be stored as a date/time string with the format yyyy-MM-dd HH:mm:ss
Timestamps and Times
These are always retrieved in the UTC timezone
Fields with Choices (and fields of type choice)
The value of the choice is retrieved, not the label. In many cases this will be an integer.
If the option to support retrieval of display values is checked, The display value field (name prefixed dv_) will contain the label of the choice.
True/False
The Boolean values, true or false.
If the option to support retrieval of display values is checked, The display value field (name prefixed dv_) will contain ‘True’ or ‘False’.
References
Will output the sys_id of the referenced record
If the option to support retrieval of display values is checked, The display value field (name prefixed dv_) will contain the display field value of the referenced record.
Lists
Will output a comma separated list of the the sys_id’s of the records in the list
If the option to support retrieval of display values is checked, The display value field (name prefixed dv_) will contain the a comma separated list of the display field values of the referenced record.
Images
These are treated as attachments. For archiving, if the attachment option migration is enabled ,both images and attachments will be recorded in the sn_sys_attachments table. For images, the file name will be the name of the image field.
Journal List / Journal
Version 6.0:
This field does not have a value and therefore need not be mapped.
Version 6.1 onwards
The display value field will be accessible, which holds a formatted list of all journal entries. The submitter, timestamp, type and comment values will be included for each entry. Only a display value field will be added during target table generation.
Journal Input / Variables
Version 6.0:
This field does not have a value and therefore need not be mapped.
Version 6.1 onwards
These fields will be excluded from table generation as they hold no value
Comments
0 comments
Please sign in to leave a comment.