- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2016 08:47 AM
I have two UI Policies. One that works for both roles and one that does not. I have not modified the default Access Controls.. Let me show you the UI Policy that works for admin and non admin roles:
Here is the UI Policy that does not work for non admin roles:
So, if I force my Department (Identifying Organization) be Partnership Audit and I have admin role, it works for me.
For someone else without the admin role, it does not work at all, even if I try changing the Department to something and back to Partnership Audit. Please help.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2016 10:22 AM
Figured it out. It so happened that the ICP field was tied to a custom imported and transformed Reference Table (u_implementing_church_partners) that had a specific role that was not added to the non-admin role person. Once I added that role to the non-admin user, it worked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2016 10:22 AM
Figured it out. It so happened that the ICP field was tied to a custom imported and transformed Reference Table (u_implementing_church_partners) that had a specific role that was not added to the non-admin role person. Once I added that role to the non-admin user, it worked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2017 03:22 PM
Good Day Rhett
We'd like to check the steps on how you manage to resolve it please. I have the same situation and trying to figure out what's wrong with my setup and it seems that UI policies added to the catalog form works only for admins, but not to a requester (no role). Was the solution implemented on your stated issue is adding a role to the non-admin? Please advise. Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2017 03:44 PM
Here is a screenshot of what I am referring to. If you look at the bottom there is a defaulted role created when the custom table is created which just appends _user. So in this case its: u_implementing_church_partners. You can change this if you wish in the roles. Otherwise, you need to add this role to a user if you would like them to view the field. Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2017 07:35 AM
Thank you Rhett, i got an idea here on how to get my problem resolved. Much appreciated.