Salesforce: check primary object is allowed #11391
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PopDaph
force-pushed
the
salesforce-primary-object
branch
from
163fea4 to
cee0089
Compare
Fraggle
approved these changes
Mar 17, 2025
tdraier
approved these changes
Mar 17, 2025
frankaloia
pushed a commit
that referenced
this pull request
Mar 17, 2025
* Salesforce: check primary object is allowed * Simplify
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Make sure the primary object is also allowed -> we were able to execute aggregate functions on Accounts without access to Account.
Tests
Locally
Risk
Can be rolled back.
Deploy Plan
Deploy front.