What's your question?
  1. Asked: September 29, 2025In:

    Why does my Flow fail when updating a record with “INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY”?

    Aman Shrivastav
    Aman Shrivastav Begginer

    The Flow user doesn’t have access to the related record being updated. Problem Explanation Flows respect object- and record-level security unless run in system context. Root Cause(s) 1. Missing record sharing 2. Flow runs in user context 3. Lookup field references restricted record Step-by-Step SoluRead more

    The Flow user doesn’t have access to the related record being updated.

    Problem Explanation

    Flows respect object- and record-level security unless run in system context.

    Root Cause(s)

    1. Missing record sharing

    2. Flow runs in user context

    3. Lookup field references restricted record

    Step-by-Step Solution

    1. Open Flow settings

    2. Enable Run in System Context (without sharing)

    3. Verify sharing rules on related object

    Edge Cases & Variations

    1. Screen Flows still respect field-level security

    2. Managed package objects may restrict access

    Common Mistakes to Avoid

    1. Assuming system context ignores all security

    2. Ignoring lookup object permissions

    See less
  2. Asked: November 22, 2025In:

    How do I fix “Too many SOQL queries: 101” in an Apex trigger?

    Aman Shrivastav
    Aman Shrivastav Begginer

    Bulkify your trigger and move queries outside loops. Problem Explanation Salesforce enforces a governor limit of 100 SOQL queries per transaction. Queries inside loops multiply quickly and exceed this limit. Root Cause(s) 1. SOQL inside for loops 2. Multiple triggers on the same object 3. RecursiveRead more

    Bulkify your trigger and move queries outside loops.

    Problem Explanation

    Salesforce enforces a governor limit of 100 SOQL queries per transaction. Queries inside loops multiply quickly and exceed this limit.

    Root Cause(s)

    1. SOQL inside for loops

    2. Multiple triggers on the same object

    3. Recursive trigger execution

    Step-by-Step Solution

    1. Collect record IDs into a Set<Id>

    2. Run one SOQL query using WHERE Id IN :idSet

    3. Store results in a Map<Id, SObject>

    4. Access data from the map inside loops

    CODE SNIPPET:
    Map<Id, Account> accMap = new Map<Id, Account>(
    [SELECT Id, Name FROM Account WHERE Id IN :accIds]
    );

    Edge Cases & Variations

    1. Use Trigger.newMap in update triggers

    2. Watch for workflow or Flow-triggered recursion

    Common Mistakes to Avoid

    1. Querying per record

    2. Ignoring recursion guards

    3. Using Limits.getQueries() only for logging

    See less