Navigating around a Precision Bridge Project

The Project Tree

When a Project is open in the Design View, the left hand side panel shows the form mappings contained in this project. A form mapping defines how records from one target table will be created or updated using records from a source table.

Greyed out form mappings are disabled and will not be run when the project is executed.

The Form Mapping List

The form mapping list shows largely the same information as the tree but allows the form mappings to be re-ordered. Ordering is often important in a Precision Bridge project, since sometimes the processing of one form mapping is dependent on a previous one. Mappings are executed in the same order that they are shown in the form mapping list and the project tree.

 

Form Mapping Details

Opening a form mapping shows the details of how the migration is going to be performed. There are several tabs, each dealing with an aspect of the migration.

• Field Mappings. Defines how the values on the target records are going to be populated. These are the heart of the migration project. There are many ways in which the target values can be constructed, and this will be explained in a later section.
• Key Mappings. Define how the source and target records are correlated, so that Precision Bridge can perform an update if a source record correlates to an existing target record.
• Source filter. Defines which source records from the source table are going to be migrated.
• Lookup queries. Define queries that can be used in field mappings to bring in values from other tables.
• Options. For most migrations, this is where you can specify whether attachments are to be migrated with the record data (among other options).
• Validation. Here you can validate the form mapping, identifying any potential issues that may prevent it from running successfully.

Some specific use cases (such as database archiving and synchronization) may have additional tabs.

Tutorial Video - Precision Bridge Navigation