If i block an account using RAC I have the problem that the Splasher no longer works on its parents. Is there any workaround for this?
theres no direct fix to this. Its kind of working as designed (as I understand). the OLAP engine doesnt think you have rights to the parent because there are no children.
depends on your implementation of RAC to determine the best case work around. Is this a limited user set or do you have a lot of users and permissions that you are managing? Perhaps programmatically loading?
The problem occurs when only some of the children are blocked.
it may sound strange but as a test, grant write access to the parent. i wonder if that will help. hard to say without seeing your exact implementation but it sounds like the denial of permissions on the child is affecting the parent. Since security is additive, allowing write on that parent could theoretically resolve the issue.
I realize thats not a great solution but at least it would help narrow down what the issue actually is.
Have you opened a support ticket yet? might be good to be preemptive about that.
I can confirm that even with WRITE permission on the parent elements the splashing does not work. Splashing only works if every base cell for the splashing target has WRITE permission. This creates a problem if you have elements which are only valid in a specific timeframe
Example: RAC with two Dimensions: * Cost_Center * Time_Month The cost center elements CC1 and CC2 (both base elements) are only valid until 2025-05 (a base element in Time_Month) and as such have WRITE permission until 2025-05 and READ after 2025-05 in the RAC. If you want to splash on consolidated elements like a cost center group which has several cost center base elements including CC1 and CC2 and the year element 2025 (which includes the months 2025-01 to 2025-12, the splashing fails.
We only managed to solve this partially via a Application Engine process which locks all base elements for the splash target which don't have WRITE permission (in this case the months 2025-06 to 2025-12). But this limits the splashing to the months 2025-01 to 2025-05 and also to custom Application Studio reports because you can't use Application Engine processes in other applications like Office Integration or Self-Service as far as i know.
