Qrew LegendWell, here's the challenge. The typical use of secure links is that you include the Access Key parameter as "&AccessKey=1234xxxxxxxxxxxxxxxxxx that must appear somewhere in the URL on top of the screen you are sitting on.
The GetAccessKey() function looks at the URL and calculates that to be
1234xxxxxxxxxxxxxxxxxx
Then typically you have a custom permission rule that compares the access key that it sees in the URL at the top of the page with a calculated access key based on that SHA256 formula, and you make a formula that says if those match then the users is allowed to view the record.
If you want to send the user to our report where all records on that report are going to be valid for the user than somehow the access key, which is at the top of the screen needs to match the calculated access key on each record.
You seem to have a situation where different EOTI type participants are allowed to see different records.
If you were sending individual links to individual records, then it would be easy because you could just copy and paste the extended URL on the target table, which includes the access key into the link that you send the user.
But if you want to send them to a report, then that means the access key free recorder has to match the access key that you provide at the top of the screen and the URL.
.
