Migrating Attachments into a BMC Remedy Server

As of Precision Bridge version 8.1, attachments can be migrated from any source server into a target BMC Remedy server.

There are a few different ways this is configured, depending on the source server type:

From BMC Remedy

If you are migrating attachments from one BMC Remedy server to another, you simply need to map the attachment fields you would like to migrate using a simple mapping.

From Other Server Types:

To migrate into a Remedy Server, you will need enable attachment migration for the form mapping and identify the attachment fields that should be filled with the incoming attachments. This is done on the Options tab for each form mapping.

For most servers, attachment migration is enabled by selecting the attachment migration option 'Fill Attachment Fields'. You will then be presented with the table of attachment fields that should be filled. This will be initially empty.

To select an attachment, use the 'Select...' button to select the set of attachment fields that you would like to populate. Attachment fields that are not selected will not have attachments added to them during migration, even once the selected fields have been filled. You must select at least one field.

Note that if your source is CSV, the migration option to activate attachment migration is 'Attachments from URL fill Selected Fields'. In addition to selecting the target attachment fields to populate, you will be required to configure the table (csv file) that will provide metadata about the attachments to be migrated. More information about this can be found in the article: CSV Source Attachment Migration - Overview

Notes on Execution

Below is an explanation of the migration process Precision Bridge will follow with regard to attachments.

• If the record itself was not migrated (due to an error) the attachments will not be migrated either.
• All attachments for the source record will be retrieved, then a check will be made to see if any already exist on the target record (if the migration is updating an existing record)
• If the attachment already exists (matching filename and size) it will not be added a second time.
• If the attachment does not exist, an empty attachment field on the target record will be identified. Only the attachment fields selected (see above) will be considered.
• If no empty attachment field can be found, the attachment will not be migrated, and an error will be noted against the attachment in the migration report. The record migration will be reported as a warning (since the record itself was migrated, but one or more attachments were not)