- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-23-2017 10:20 PM
Hi all,
I have searched and can't find anything, so here goes.
Is there any way, be it by a business rule (with a custom script?), or an ACL, to prevent sensitive data which is stored in field 'xyz' on an Incident record from being exported via any of the export methods?, it's kind of like wanting an ACL where the 'operation' is 'export', to cover all of the different ways it could be exported.
For example, sensitive data is stored in field 'xyz' on Incidents, there's a requirement for this data to not be able to be exported through any of the export methods in the system, so either a Scheduled Export, or when a fulfiller right-clicks on the Incident record and selects Export (using any option).
This sensitive data is still required to be seen by the fulfiller on screen obviously, so they still need read/display/update access.
I can't think of any sort of 'cover all the bases' kind of way for doing it.
Any ideas would be greatly appreciated
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2022 08:22 PM
Hi dpe,
Appreciate the suggestion, but this doesn't address the client's requirement.
As this post is quite old, just to wrap it up, this 'no export' requirement was withdrawn by the client.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2017 02:33 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2017 03:14 PM
Hmm, restricting access by user role is not exactly what the client is after, but thank you anyway for your response.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-27-2017 08:58 AM
If field xyz is custom field then you could look at using encrypted field - this would only be visible to users with the encryption context and could not be exported by someone without it. Take a look at: Encryption support
Warning - there are gotchas with this approach as you cannot run any BR's, client scripts, search, etc functions against encrypted fields.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2022 08:22 PM
Hi dpe,
Appreciate the suggestion, but this doesn't address the client's requirement.
As this post is quite old, just to wrap it up, this 'no export' requirement was withdrawn by the client.