Tracking ID at application level is not available for mapping during data import
- Application B has the tracking ID at Application level (Not at System level)
- Application A has cross reference to application B
- When I am importing data in application A (the sheet has a column for Tracking ID of application B as well), I don't see the XREF field in the drop down to be available for mapping to the column in my sheet.
- However, when I make the Tracking ID of application B at System Level (not Application ID type), the XREF field appears in the drown down for mapping.
Is this a know issue or is it the expected behavior of Application level tracking ID fields ?
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
As far as I know this is 'normal', cannot import into aplication usng application level tracking ID as the unique identifier. Have also found ID prefixes get in the way of importing if you forget to remove the prefix.
Well, if this is the normal behavior then I think RSA must fix this. There is no use of Application level tracking ID if it cannot be used as an unique identifier for data import purposes, because we then need to have a System level tracking ID in background anyways. My another suggestion to RSA would be to have the capability of getting Index rebuild automatically when Application level tracking ID is promoted to System level. @ Please consider this if you read this.