Troubleshooting

The following messages can be found in the record-level reporting output:

Message	Status	Meaning
Transform Map Script Used	Success	The migration was successfully executed using the Import Set (Scripted) method.
UI Policy Records [created:0 updated: 1 errors: 0] | variable orders updated: [6]	Success	Successful result of migration using the virtual table for Order Guide record creation.
No Changes Made	Skip	The migration has been configured to skip if entry exists on target. This is configured in the options tab for the individual mapping. Can also occur when using a virtual table when no differences found between the source and target record.
Another source record is being migrated for this key	Skip	The record was skipped because it was identified as a duplicate based on the Key Mapping defined for the corresponding mapping.
Target Entry Exists and No Updates Allowed	Skip	The migration has been configured to skip if entry exists on target. This is configured in the execution options for the project as a whole.
No entry retrieved when running lookup query [lookup query name]	Skip	The corresponding field mapping (of type Lookup), has a No Match Action set to Skip when no record is found.
Attachment migration was cancelled before completion. Attachments may not have been migrated.	Warning	For some reason (usually user cancellation during a migration) the attachment migration failed to complete for this record. The attachments may or may not have been migrated and this needs to be either checked manually or corrected by re-running the migration of this record
The File <filename> is too large for migration	Warning	Occurs if a file being migrated is larger than the maximum size specified in execution options
Failed to delete duplicate of <filename> on target entry	Warning	If an attachment is being replaced during the update of a record, the new attachment was migrated, but the existing one was not removed. Manual intervention will be required to remove the old attachment.
Only the first 200 list values were migrated	Warning	For Service Now -> Service Now When migrating a list field, the maximum number of values in the source list that will be migrated is 200. If the list is larger than this, the remaining values must be entered manually if required
Source ID List contains an entry or entries that cannot be matched on the target server	Warning	For Service Now -> Service Now When migrating a list field with the no match option set to ‘Warning’ this warning is shown if one of the list values on the source could not be mapped to a target value. The list item will be excluded from the target list.
Source ID List contains an entry or entries that match on more than one entry on the target server	Warning	For Service Now -> Service Now When migrating a list field with the no multi option set to ‘Warning’ this warning is shown if one of the list values on the source maps to more than one target value. The list item will be excluded from the target list.
A source reference value maps to multiple target values	Warning	For Service Now -> Service Now When using the ID replace mapping, with multiple match option set to ‘warning’, this warning is shown if the one of the detected source sys_id values maps to more than one target value (using the display value to map with)  The first match will be used, but this should be checked manually to make sure it is correct.
The value associated with <source sys_id> does not map to any target values	Warning	For Service Now -> Service Now When using the ID replace mapping, with no match option set to ‘warning’, this warning is shown if the one of the detected source sys_id values does not map a target value (using the display value to map with)  The id will remain unchanged in the target string
There more than 100 references to be changed. Only the first 100 will be updated	Warning	For Service Now -> Service Now When using the ID replace mapping for an encoded query string, there is a limit of 100 id’s that can be replaced in a single string. Further id’s will remain unchanged and should be changed manually.
The field <reference field name> references a table that has no display field	Warning	For Service Now -> Service Now When using the ID replace mapping for an encoded query string, the reference field references a table for which no display field has been identified. This means that the id cannot be mapped to a target value and will remain unchanged in the target string
The field <reference field name> does not exist on the target server, or does not reference another table	Warning	For Service Now -> Service Now When using the ID replace mapping for an encoded query string, the a field name has been found that which does not exist on the target table. Can also occur if the field definition on the target table is corrupted. The sys id will remain unchanged in the target string
Dot walking is not supported for field	Warning	For Service Now -> Service Now When using the ID replace mapping for an encoded query string, a field name was found to contain a ‘.’ Character. This indicates a ‘dot walk’ operation to reference a field within the referenced record. This is not supported and the value will be left unchanged.
The target display field cannot be identified	Warning	For Service Now -> Service Now When using the ID replace mapping for a standalone id or list, the table used to obtain the sys id on the target does not have a display value, hence the source id cannot be mapped using display values. The value will be left unchanged.
More than 200 values in the list. Only the first 200  have been updated	Warning	For Service Now -> Service Now When using the ID replace mapping for a list value, the source list contains more than 200 values. The maximum supported is 200, the remainder must be added/updated manually.
The scripted Import Set Item did not return a recognised status <and sys_id>	Warning	This can occur in some virtual table migrations where the status_message value returned is not of the correct format, which should be: <status>;<sys_id>;<message> The actual operation the script performed may have completed correctly, but this cannot be verified.
Control characters detected in one or more values in this entry were removed before migration	Warning	In Service Now target servers, a retry occurs if control characters cause a corruption of the SOAP create/update request sent to the target server. This warning is shown if these control characters were removed and the retry succeeded. It is likely that no action is required.
Failed to generate target value for [Field Name]  [Mapping Name]-Reference Mapping - No mapping found	Error	The corresponding field mapping (of type reference), has a No Match Action set to 'Log Error' if no matching record is found.  Change to Skip or Set Null if required.
No entry retrieved when running lookup query [lookup query name]	Error	The corresponding field mapping (of type Lookup), has a No Match Action set to Log Error when no record is found.  Change to Skip or Set Null if required.
Entry contains a NULL key field value	Error	A record has been found on either source or target table that has a NULL value for the field(s) defined on the Key Mapping on the corresponding Form Mapping.   Change the Key Mapping by selecting the option to Allow NULL values in Key Fields.
Failed to Post Attachment Data	Error	Can occur if the migration of an attachment takes longer than 60 seconds.  See separate article on how to address this.
Operation against ... was aborted by business rule	Error	Occurs if the migration activates a ServiceNow business rule which prevents the record being created/updated.  See separate article on how to address this.
Unrecognised Response from Import Set Migration	Error	Indicates that the transform map script used on the target failed to set the status value in the response to one of the following values: created, updated, skipped, ignored, error
No Mapped target record could be found	Error	The key mapped field values do not identify a target record. Only raised if the update action is set to ‘Log Error’
Multiple matching target records found for update	Error	The key mapped field values identify more than one target record. Only raised if the multiple match option in the Key Mapping is set to ‘Log Error’
Target Entry Exists and No Updates Allowed	Error	Key mappings identify a target record and  the ‘on update action’ in the Form Mapping options or execution settings is set to ‘Log Error’
Target Entry Does not Exist and No Creates Allowed	Error	Key mappings do not identify a target record and the ‘on create action’ in Form Mapping options or execution settings is set to ‘Log Error’
Soap Parse Error occurred while Processing this Batch	Error	May sometimes occur if a non printing character is present in the Service Now source data. Note this error affects the entire batch of source records being retrieved, so to identify the record causing the issue, it may be necessary to reduce the chunk size down to 1 for the field Mapping temporarily.
ERROR: Failed to generate target value for macro Failed to execute Soap Lookup for table sys_ui_macro on server [server name] [com.glide.processors.soap.SOAPProcessingException: Field(s) present in the query do not have permission to be read [SOAP-ENV:Server]	Error	Caused by ACL restricting access to read the name field on sys_ui_macro table. Update the ACL and set the Admin overrides option to resolve this as in the screenshot below.

Enabling access to the sys_ui_macro name field used by Precision Bridge Macro Reference Mappings: