Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Discover how organizations are unlocking new revenue streams: Watch here
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Edit Field Data on Open

Is it possible to edit the contents of a data field via API? I have a simple formula that I would like to execute based on who is opening the document. It is basically a user sensitive scramble to allow a user to see all data, but have everything but their own data be deidentified.

Thanks!!

1 Solution

Accepted Solutions
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

There is no API that allows you to update field contents. A couple suggestions for your problem.

1. Only display the data via expressions where you could scramble the data. This would not be secure if you allow Server Collaboration because the user could create an object using the unscrambled data.

2. In the load script repeat the data for each user, keyed to the userid, with the other users data scrambled. Then use Section Access to reduce to the correct set for each user on open.

-Rob

View solution in original post

2 Replies
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

There is no API that allows you to update field contents. A couple suggestions for your problem.

1. Only display the data via expressions where you could scramble the data. This would not be secure if you allow Server Collaboration because the user could create an object using the unscrambled data.

2. In the load script repeat the data for each user, keyed to the userid, with the other users data scrambled. Then use Section Access to reduce to the correct set for each user on open.

-Rob

Not applicable
Author

Interesting... I hadn't thought of using separate fields. We are talking about hundreds of users in the system though we could probably get by with about 20 unique reduction profiles. Even if that mushroomed to 40-50 fields, I don't think its anything terribly taxing on the server during a reload since its just a customer ID table with <1,000 records.

Thanks for the great suggestion Rob!