How can I prevent data feeds from creating duplicate records on the RSA Archer platform?
I have 3 separate applications:
- Risk Libraby
- Processes
- Risk app
Processes can be linked to multiple risks from the Risk Library (via cross-reference). One process can be associated with many risks from the Risk Library (P1 → R1, R2 and P2 → R2, R3, R4).
The end user can show up at any time and add risks to the process record.
Data transfer runs that create separate entries in the Risk application for each associated risk based on the values in the cross-reference in the Processes application, as shown below:
P1 → R1
P1 → R2
P2 → R2
P2 → R3
P2 → R4
And it removes associations from the cross-reference in the Processes app (so the cross-reference is empty after starting the feed).
Now I want how I can prevent the creation of duplicate entries in the Risk application. Ex. if the P1R1 record is already created in the Risks app and the end user after 2 months links R1 to P1 again (in a cross-reference), he should not create P1R1 again in the Risk app.
I hope I made it clear. Any solution or any other work around this requirement would be kindly appreciated. thanks in advance
source to share
This is an interesting case that you described there.
First of all, I think you are not providing a complete picture of the relationship / design you have. 
Take a look at the diagram I created based on your requirements. You said that your data feed creates new records in the Risk application and simultaneously updates the records in the Processes application. This cannot be done on the same data channel unless the two applications are linked through a different cross-reference. Or, you are using a different data feed to update records in the Processes app (and you didn't mention that).
I will try to provide you with the best answer based on what you have shared. I am assuming there is a relationship between the Rick Application and the Processes, although you did not mention it. 1. Update your data feed configuration to make sure it will create new entries in the Risk app. 2. Update your data feed to use the Process + Risk combination as the key during import. The corresponding field must be created in the Risk application. Please note that you do not need to change the key field in the Risk application itself. You can calculate the string value for this import key in the data feed itself. If you do this, using "Create Only" and the "Process + Risk" data import key, your data feed will only create new unique records. 3.By exploiting the missing link between Risk App and Processes, this data feed can override the cross-reference pointing to the risk library located in the Processes app. You can use a static text box to override it in the data feed itself.
Tanveer,
This solution should work. Note. This is the best answer I can give you based on the limited information you have shared.
Good luck!
source to share