-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guest user changes break DLRS Scheduled rollups #987
Comments
Just wanted to chime in and say this is still an issue and affecting many of my clients. The only workarounds I know of right now are:
|
We face the same issue |
We're also running into this with our clients and it's a pretty big issue as we have a lot of clients that use Sites to collect data. Any input or advice would be greatly appreciated. |
I am receiving the error message, "insufficient access on cross reference entity" and I am not a guest user, I am the System Administrator. Can anyone advise on how I can resolve this issue. The assistance is greatly appreciated |
I believe I am experiencing this now on code that has been running for years using V4SF (Volutneers for Salesfroce) and DLRS together to help keep things straight. It is my understanding that this is because some child records that the guest site (V4SF) user are updating are in scheduled mode (incremental) and that the only workable solutions right now are to change the scheduled (incremental implied) to scheduled full or realtime. |
This problem first manifest as "duplicate parents" error and then when I added read-only permission as "inadequate access / Read only access" error. Fixed by changing to real-time mode. |
Duplicate of #375 |
Describe the bug
In winter 21 Salesforce is enforcing guest user restrictions in all orgs. These restrictions include:
It is this second setting that causes issues for rollups in Scheduled mode. This causes an insurmountable issue for DLRS rollups in Scheduled mode. Scheduled mode will insert or update in the Scheduled Items object. This object has a unique key based on Parent ID and CMDT ID. If the guest user triggers a Scheduled rollup, and a Scheduled Item does not exist, then the guest user is able to create a Scheduled Item without issue. If the guest user triggers a Scheduled rollup, and a Scheduled Item does exist, then an error is thrown when the guest user attempts to update that Scheduled Item.
To Reproduce
I have created this SFDX repo to reproduce this error
Steps to reproduce the behavior:
Expected behavior
Both contacts are created without error.
Actual behavior
The second contact results in an error because the guest user cannot update the Scheduled Item created with the first contact.
Additional context
The only way I know to fix this issue is to change the code to execute without sharing.
The text was updated successfully, but these errors were encountered: