This documentation supports the 18.05 version of Remedy ITSM Deployment.

To view the latest version, select the version from the Product version menu.

Correcting invalid field mappings in join forms

This topic provides information about identifying invalid field mappings in a join form, and the procedure to correct the invalid field mappings.


  • If you upgrade BMC Remedy IT Service Management (ITSM) from version 7.x.xx, and if invalid field mappings are present, then the upgrade fails. You must correct the invalid field mappings before you continue the upgrade.
  • You can find whether and where fields are used with the CI Data Migration Utility (DMU), which is a Java application called cimig.jar. The DMU is available for the BMC Remedy ITSM upgrade. The earliest when you can use the DMU is during upgrade if Phase 1 encounters an issue, and you must fix the issue before proceeding with the upgrade. If there are no issues during Phase 1, the DMU is available at the end of Phase 1 and remains available even after upgrade has completed. For more information about using the DMU, see Finding whether and where fields are used in the system from the BMC Remedy ITSM online documentation.

When you upgrade BMC Remedy ITSM, if the installer detects invalid field mappings, you can refer to the CIDataMig.log file to identify the forms and fields that require correction.

A mapping is considered invalid if a field has been mapped from the secondary form of one of the identified self join forms. Instead, the field should be mapped from the primary form. During the upgrade process, these join forms are modified, and the secondary form is replaced by the AST:Attributes form. For more information, see Join architecture  in BMC Remedy ITSM online documentation.

If you add custom attributes to the CMDB Classes and add the attribute to the form specified in the CIDataMig.log file using the Sync Asset UI with CMDB utility, the utility adds the custom attribute from the primary side of the join form. The custom attribute might not be visible on the in the main view of the form. Because you might not see the custom attributes on the main form, there is a possibility that you add it manually from the secondary form, which results in a duplicate attribute. The duplicate attribute causes invalid field mapping on the join form. In such a case, to make the field visible on the main form, create an overlay and bring the fields from hidden view to main view or to the view where you need to place the field.

The following image shows a sample duplicate attribute.

Use BMC Remedy Developer Studio to correct the join form by deleting the invalid field mapping. The source field can be mapped from the primary form of the join form, with the same field ID assigned again to preserve any references.

To correct an invalid field mapping in the join form

  1. Open the CIDataMig.log file and look for reportFieldMappings, as in the following sample entry:

    [2013-07-30 12:17:53.724 -0700] scanFieldMappings CIAttribDataMigration
    INFO: Checking the ITSM fieldMappings 
    [2013-07-30 12:18:05.297 -0700] reportFieldMappings
    CIAttribDataMigration INFO:
    [2013-07-30 12:18:05.297 -0700] 
    reportFieldMappings CIAttribDataMigration INFO: Join Form Name - AST:ComputerSystem 
    [2013-07-30 12:18:05.297 -0700] 
    reportFieldMappings CIAttribDataMigration INFO: Primary Form - BMC.CORE:BMC_ComputerSystem 
    [2013-07-30 12:18:05.297 -0700] 
    reportFieldMappings CIAttribDataMigration INFO: Secondary Form - BMC.CORE:BMC_ComputerSystem
    [2013-07-30 12:18:05.297 -0700] 
    reportFieldMappings CIAttribDataMigration INFO: Source Field ID - 600000320 
    [2013-07-30 12:18:05.297 -0700] 
    reportFieldMappings CIAttribDataMigration INFO: Database Field ID - 536870913 
    [2013-07-30 12:18:05.335 -0700] 
    reportFieldMappings CIAttribDataMigration INFO: Join Field Name - Alternate Name 
    [2013-07-30 12:18:05.335 -0700] 
    reportFieldMappings CIAttribDataMigration INFO:
    [2013-07-30 12:18:44.254 -0700]
    scanFieldMappings CIAttribDataMigration
    INFO: Finished checking ITSM field Mappings
  2. Open the join form that is listed in the log file.

    For example, open the AST:ComputerSystem form.

  3. On the join form, locate the field, such that the ID of the field matches the Database field ID from the CIDataMig.log file entry.
    For example, the field ID of Alternate Name is 536870913, matches the Database field ID in the CIDataMig.log file entry.
  4. Delete the identified field from the form and save the form.
  5. From the main menu, selectForm > Add/Remove Fields In View...
  6. Move the identified field from the Fields Not in View list to the Fields in View list and click OK.
    For example, move the field Alternate Name to the Fields in View list.
  7. Reposition the field in the view, if required, and save the form.
    You might need to create an overlay on the view.
  8. For all the invalid field mappings identified in the CIDataMig.log file, repeat steps 1 through 7.


    Document all the changes you make. You might need to repeat the steps if you restore the database.

  9. Save the form and restart the BMC Remedy ITSM upgrade process.


    If the upgrade fails at this stage, you do not need to restore the database.

For information about changes to BMC Remedy ITSM lifecycle fields, see  Changes to the BMC Atrium CMDB for BMC Remedy ITSM  in BMC Remedy ITSM online documentation.

Was this page helpful? Yes No Submitting... Thank you