Conversion steps: Contact Information - HxGN EAM - 12.0.1 - Feature Briefs - Hexagon

HxGN EAM Externcode Conversion

Language
English
Product
HxGN EAM
Search by Category
Feature Briefs
HxGN EAM Version
12.0.1
  1. Identify the Contact Information Codes (cti_code) and Contact Information Organizations (cti_org)for all Contact Information records where the Contact Information External Contact ID value (cti_extern_contactid)is not null.

  2. Copy the attached .csv file to your local folder and populate it with the Contact Information Code, Contact Information Organization, and Contact Information External Contact ID details.

    The updated_r5contactinfo_externcode.csv document is attached to this PDF in the Attachments pane.

    The first row of the .csv file should not be modified.

  3. The resulting .csv file entries would follow the below example:

    R5CONTACTINFO_1

  4. Update the Contact Information External Contact ID values for each of the Contact Information records in the csv file based on the following criteria:

    1. The value must be unique across all users for the customer, and preferably, globally unique.

    2. The value must never be null in the IDP’s database.

      This value must be sent in the SAML response from the IDP against the claim, http://schemas.hexagon.com/claims/Identity.

  5. It is recommended to use UPN. However, any value meeting the above criteria can be used.

  6. The resulting .csv file entries would be something as follows:

    R5CONTACTINFO_2

  7. Copy the attached powershell script to your local folder and execute it by providing the necessary inputs. The R5 user will be used to execute the script to update the Contact Information records in the R5CONTACTINFO table.

    The update-r5contactinfo-extern-code.ps1 document is attached to this PDF in the Attachments pane.

    A sample execution run is as follows.

    R5CONTACTINFO_3

    The powershell script will update the Contact Information External Contact ID column of each Contact Information record populated to the csv file in the R5CONTACTINFO table and display a summary upon completion. If there are any errors while updating the records, these errors are logged to a separate file whose details are also provided upon completion.