How to create records with combined key field?
Application 1 with records
Application 2 with records
Application 3 is empty
Application 1 links with Application 2 through cross-reference filed.
How can we create records in Application 3 with key filed combined from Application 1 key and Application 2 key using Archer-to-Archer Data Feed?
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
I tried to do so, but how such filed should be configured? I tried different formulas but always got errors. I easily can make calculated filed in data feed that will concatenate two fileds from one level, but how I can create calculated field that will referes different levels (I mean cross-reference). The formula that works in formula builder in application manager does not work in calculated filed in Data Feed.
The calculated field in the data feed can only reference fields from the source report. So you'll need to ensure that that report contains the fields you need to concatenate into App3.
You might also consider adding two cross reference fields in app3 - one to reference app1 and the other to reference app2. You could then create a key field in app3 which is calculated to create a value of your choice of app1 and app2 fields.
If any of the applications are leveled
then this adds complexity. I suspect you'd need one data feed per level.
My report does contain fileds that I need.
I am not sure that clearly understand why I should do cross reference fileds in appp3
So my report looks like:
TESTAPP2 is cross reference field to TESTAPP2 application.
My data feed (that targets TESTAPP3) and my question:
I'm late to the rodeo (found this while looking for why the my DFM is only populating the last cross reference in a list of cross references) but the way this can be done in that specific case is:
= [ArcherRecord.TEXTFIELD1] & “-“ & [TEXTFIELD2]
Where the dot-notation is used to reference the parent level and no notation is required if you are creating in the child level. Also, if I understand what you were looking for (4 months ago) it looks like the calculated field you created is one level too high and needs to be created off of the Reference_471 level.