You’re offline. This is a read only version of the page.
Announcements
27
Hello all,
I have a situation where I need to dynamically allow access to groups of records depending on what we call an officer code. The idea would be to have an entity to list all the officer codes with the owner of the officer number as the owner of the record in dateverse. This entity would then have a 1:N to another entity with cascade all for reparent (the security is user only for each entity). As fair as my knowledge goes, reparent relationship behavior should inherent the access right from the parent entity record owner to the related record. This is not working as described by many sources ( Link1, Link2 ), Here are just a couple. After trying every combination, the relationship allows for sanity sakes I tried the share cascading to see if the cascading logic is supposed to do what I am reading, and it behaves like expected giving access to child records that the parent is linked to. I don't want to manage thousands of shares (not to mention possible load issues when there are millions, so I move on to try access teams. Got the access team set up as described by this link to simply test. As it seems it was to utilize the parent relationship behavior to cascade the access. yet again my testing does not allow any access because the cascading is not working for reparent. Would anyone have any idea what would be going on? I have checked both plugin logs and system log/jobs and nothing is happening regarding the access rights or cascading jobs. Any help would be appreciated.
Share
Report
All responses (
Answers (
