Making a Related List read-only for a specific role
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2017 03:51 AM
Hello,
I have a requirement to make a Related List on a form read-only (they want it to be a static list with just information). They do NOT want the end user to be able to click on anything on that list, including the Information Icon. I've done quite a bit of research into this and haven't been able to find a solution, so I was wondering if anyone out there had ever run into this type of requirement before and if there's a solution. Thank you in advance!
Regards,
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2017 04:01 AM
Related List -> Right click on any column -> Configure -> List Control
List edit type -> Disable list editing
This disables for all users.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2017 04:23 AM
Thank you for your quick response Gowrisankar. Unfortunately, simply disabling the list edit feature won't work as they do not want the end User to be able to click on anything, they just want a static form (like if you were to print off an Excel spreadsheet).
Regards,
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2017 04:06 AM
Michael Grimm wrote:
Hello,
I have a requirement to make a Related List on a form read-only
If it's the list records itself, then consider an ACL on the list to prevent write.
They do NOT want the end user to be able to click on anything on that list, including the Information Icon.
Being able to navigate to list records is still considered a read-only operation.
It sounds like you want to constrain the functionality, not just security, here. Is that user-friendly or user-hostile?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2017 04:21 AM
Good Morning Dave,
Thank you for the quick response. Yes, this is more along the lines of limiting the functionality, but to a targeted audience. I already put read ACLs in place for the role in question. The reason for this is that there will be external customers looking at this information and they don't want them to be able to access it. What I'm thinking is creating a new view for the table in question and just limiting the fields on the form for that table to generic things that the User would be able to see, without giving up any sensitive information. From what I've been researching, it doesn't sound like there's a system-friendly way to accomplish exactly what I'm looking to do.
Regards,
Mike
