This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

Fixing non-permitted modifications for fields

This topic provides instructions for fixing non-permitted modifications to fields.

To change the data type

If your field does not contain data that should be saved, delete the field on StagingServer and copy the corresponding field from ReferenceServer to StagingServer.

If the field does contain data that should be preserved, perform the following steps:

  1. On StagingServer, rename the field.
  2. Use the ARCHGID utility to change the ID to the customer range.
    The ARCHGID utility is not supported. For information about this utility, see https://communities.bmc.com/communities/docs/DOC-19172.
  3. Copy the corresponding field from ReferenceServer to StagingServer.
  4. Copy data to this field if the data is compatible.
  5. Delete the field that you renamed in Step 1.
  6. Save the form.

To change the Column properties on View and Vendor forms

  1. On StagingServer, open the View or Vendor form and the form view that contains the field, and select the field.
  2. On ReferenceServer, select the corresponding field.
  3. On StagingServer, set the field's Column property to the same value as that of the field on ReferenceServer.
  4. Save the form.

To change the Name

  1. On StagingServer, open the form and the form view that contains the field, and select the field.
  2. On ReferenceServer, select the corresponding field.
  3. On StagingServer, set the field's Name property to the same value as that of the field on ReferenceServer.
  4. Save the form.

To change the Length Units property of character fields

If your field does not contain data that should be saved, then delete the field on StagingServer and copy the corresponding field from ReferenceServer to StagingServer. If the field does contain data that should be preserved, perform the following steps:

  1. On StagingServer, rename the field.
  2. Use the ARCHGID utility to change the ID to the customer range.
    The ARCHGID utility is not supported. For information about this utility, see https://communities.bmc.com/communities/docs/DOC-19172.
  3. Copy the corresponding field from ReferenceServer to StagingServer.
  4. Copy data to this field if the data is compatible.
  5. Delete the field that you renamed in Step 1.
  6. Save the form.

To change the Column field properties for Parent field ID, Data field ID and Data Source

For each field where these properties have been changed, set the values on StagingServer to match those on ReferenceServer.

To change the Entry Mode to Display

If the out-of-the-box field's Entry Mode is Display, and the StagingServer field is not, complete the appropriate steps:

If the field does not contain data that must be saved:

  1. Delete the field on StagingServer.
  2. Copy the corresponding field from the ReferenceServer to StagingServer.

If the field does contain data that should be preserved, perform the following steps:

  1. On StagingServer, rename the field.
  2. Use the ARCHGID utility to change the ID to the customer range.
    The ARCHGID utility is not supported. For information about this utility, see https://communities.bmc.com/communities/docs/DOC-19172.
  3. Copy the corresponding field from ReferenceServer to StagingServer.
  4. Save the form.

To change the field type

If your field does not contain data that should be saved, then delete the field on StagingServer and copy the corresponding field from ReferenceServer to StagingServer. If the field does contain data that should be preserved, perform the following steps:

  1. On StagingServer, rename the field.
  2. Use the ARCHGID utility to change the ID to the customer range.
    The ARCHGID utility is not supported. For information about this utility, see https://communities.bmc.com/communities/docs/DOC-19172.
  3. Copy the corresponding field from ReferenceServer to StagingServer.
  4. Copy data to this field if the data is compatible.
  5. Delete the field that you renamed in Step 1.
  6. Save the form.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments