Help on Calculated cross reference field
Hi team,
We have Audit Engagement application within which we have Key Controls and Crunchy Questions has the cross references from this application. Now, we are adding a new section to track Data Analytics at Key Controls level. Within this new section, we would like to pull the Crunchy Questions that were created for the respective Engagement of the key Controls and make the selection editable for the user to remove if any of the Crunchy Questions is not applicable for DA.
My solution was to create a calculated cross reference field to Crunchy Questions from Key Controls applications by mapping the Audit Engagement from both the apps. This works to display only those Crunchy Questions that are being created for the Engagement. However, the other requirement is we need to make this editable for the user to deselect as well. Any thoughts how to accomplish this?
-
Hi Naresh,
We did something very similar to this for our Third Party Management team. One way to accomplish the removal of the desired records is to allow the user to have inline edit to a field which will change the criteria that allows the records to be associated in the first place. Depending on what the criteria is that you are using for the calculated cross-reference, you can possibly add another calculated filter that must also be true along with the other criteria you have and when that criteria becomes false, it would hopefully disassociate the record. Now I have had issues with calculated cross-references updating properly once the criteria changes so another option is to not use a calculated cross-reference but use a data feed to associate the questions and then allow removal that way. Not knowing exactly what challenges you would face in doing that I'm not sure that is an option for you. In the old days before calculated cross-references, we had to use CAST fields between the two applications for which you wanted to associate a set of records and then use a data feed to populate those records to the target application. Archer does not like the use of CAST fields but I never had any real issues with them and was able to essentially accomplish what calculated cross-references ultimately gave us. I don't know if any of this will help you but thought I would reach out just encase.
0
Please sign in to leave a comment.
Comments
1 comment