Important Update: Archer Community Scheduled Maintenance on November 23–24 - New Community Launching Soon! Learn More..

cancel
Showing results for 
Search instead for 
Did you mean: 
100% helpful (1/1)
KB-Sync1
Archer Employee
Archer Employee

Article Number

000033142


Applies To


Product(s): Archer
Version(s): All Versions
Primary Deployment: On Premises/AWS Hosted/AWS SaaS

Description


In trying to perform a Data Import and map the fields from the source to the target application, there is a Cross-Reference field not listed in the Application Fields drop-down.

Resolution


An Application Tracking ID cannot be used for mapping a cross -reference field
  • If the key field for the related application is a Tracking ID field that is configured as an Application ID, it will not be listed in the application fields and cannot be used for mapping.
  • In the Archer GRC online documentation, see the article Unique Identifiers. This article lists the field types that can be used to uniquely identify a record.  In regard to Tracking ID fields, it states: Tracking ID ("System ID" only) - You can only use the Tracking ID field as a key field if it is configured as System ID. If configured as Application ID, it is not available for use as a key field.

Solution:  If a Tracking ID field is used to map a cross-reference in a data feed, it must be a System ID.

Version history
Last update:
‎2024-09-21 07:01 AM
Updated by: