Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Why are my Salesforce reports showing incorrect totals?
The report summary level or field type is misconfigured. Problem Explanation Reports aggregate data based on grouping and field data types. Text fields won’t sum correctly. Root Cause(s) 1. Formula fields returning text 2. Incorrect grouping level 3. Filters excluding records Step-by-Step Solution 1Read more
The report summary level or field type is misconfigured.
Problem Explanation
Reports aggregate data based on grouping and field data types. Text fields won’t sum correctly.
Root Cause(s)
1. Formula fields returning text
2. Incorrect grouping level
3. Filters excluding records
Step-by-Step Solution
1. Verify field data type (Number/Currency)
2. Check report grouping hierarchy
3. Recalculate summaries
Edge Cases & Variations
1. Joined reports calculate separately
2. Row-level formulas override summaries
Common Mistakes to Avoid
1. Summarizing formula text fields
See less2. Ignoring report filters
Why does my Salesforce report not show newly created records?
The report filter excludes recent data or uses the wrong date field. Problem Explanation Reports rely heavily on date filters and ownership context. Root Cause(s) 1. “Created Date” filter set incorrectly 2. Record owner mismatch 3. Private sharing model Step-by-Step Solution 1. Adjust date filter toRead more
The report filter excludes recent data or uses the wrong date field.
Problem Explanation
Reports rely heavily on date filters and ownership context.
Root Cause(s)
1. “Created Date” filter set incorrectly
2. Record owner mismatch
3. Private sharing model
Step-by-Step Solution
1. Adjust date filter to “All Time”
2. Verify record ownership
3. Check report running user
Edge Cases & Variations
1. Dashboard running user affects visibility
2. Joined reports may filter differently
Common Mistakes to Avoid
1. Assuming admin sees everything
2. Ignoring sharing rules
See lessWhy does my Salesforce REST API upsert create duplicates instead of updating?
The External ID used for upsert is missing or not unique. Problem Explanation Upsert relies on External IDs to decide whether to insert or update a record. If Salesforce can’t match one record exactly, it inserts a new one. Root Cause(s) 1. External ID field not marked correctly 2. Null external IDRead more
The External ID used for upsert is missing or not unique.
Problem Explanation
Upsert relies on External IDs to decide whether to insert or update a record. If Salesforce can’t match one record exactly, it inserts a new one.
Root Cause(s)
See less1. External ID field not marked correctly
2. Null external ID value in request
3. Duplicate external ID values
Step-by-Step Solution
1. Mark field as External ID + Unique
2. Validate payload includes external ID
3. Clean existing duplicate records
Edge Cases & Variations
1. Case sensitivity matters for text external IDs
2. Bulk API handles failures differently
Common Mistakes to Avoid
1. Using Name field as External ID
2. Skipping uniqueness constraint
Why does my LWC not refresh after record update?
The wired data is cached and not refreshed explicitly. Problem Explanation Salesforce caches wire adapters. UI won’t update unless data is refreshed using refreshApex. Root Cause(s) 1. Missing refreshApex 2. Using imperative Apex without state updates 3. LDS cache not refreshed Step-by-Step SolutionRead more
The wired data is cached and not refreshed explicitly.
Problem Explanation
Salesforce caches wire adapters. UI won’t update unless data is refreshed using
refreshApex.Root Cause(s)
See less1. Missing
refreshApex2. Using imperative Apex without state updates
3. LDS cache not refreshed
Step-by-Step Solution
1. Store wired result reference
2. Call
refreshApex(this.wiredResult)3. Use
getRecordNotifyChangeif using LDSEdge Cases & Variations
1. Cacheable Apex requires explicit refresh
2. Cross-component updates need LMS
Common Mistakes to Avoid
1. Expecting auto-refresh
2. Re-rendering component manually
Why does my Apex HTTP callout fail with “Callout not allowed from this context”?
Callouts are not permitted from synchronous trigger execution. Problem Explanation Salesforce restricts HTTP callouts from certain contexts, including standard triggers and some Flow actions. Root Cause(s) 1. Callout inside trigger 2. Callout inside non-async Apex 3. Mixed DML before callout Step-byRead more
Callouts are not permitted from synchronous trigger execution.
Problem Explanation
Salesforce restricts HTTP callouts from certain contexts, including standard triggers and some Flow actions.
Root Cause(s)
See less1. Callout inside trigger
2. Callout inside non-async Apex
3. Mixed DML before callout
Step-by-Step Solution
1. Move callout logic to
@future(callout=true)or Queueable2. Invoke async method from trigger
3. Ensure no DML before callout in same transaction
Edge Cases & Variations
1. Platform Events allow callouts asynchronously
2. Named Credentials simplify auth handling
Common Mistakes to Avoid
1. Calling APIs directly from triggers
2. Ignoring transaction order
Why does my Salesforce deployment succeed but features don’t work?
Metadata deployed successfully, but required settings or permissions are missing. Problem Explanation Deployments don’t automatically configure permissions, licenses, or settings. Root Cause(s) 1. Missing permission sets 2. Feature not enabled in target org 3. Post-deployment steps skipped Step-by-SRead more
Metadata deployed successfully, but required settings or permissions are missing.
Problem Explanation
Deployments don’t automatically configure permissions, licenses, or settings.
Root Cause(s)
See less1. Missing permission sets
2. Feature not enabled in target org
3. Post-deployment steps skipped
Step-by-Step Solution
1. Verify feature activation
2. Assign permission sets
3. Validate profiles and access
Edge Cases & Variations
1. Sandboxes differ from production
2. Scratch orgs need manual setup
Common Mistakes to Avoid
1. Assuming deployment = configuration
2. Ignoring post-deploy checklist
Why does my Salesforce API call return “INVALID_SESSION_ID”?
The access token or session ID has expired or is invalid. Problem Explanation Salesforce API sessions expire or become invalid when reused incorrectly or when IP relaxations are misconfigured. Root Cause(s) 1. Expired OAuth token 2. Incorrect login endpoint 3. IP restriction mismatch Step-by-Step SoRead more
The access token or session ID has expired or is invalid.
Problem Explanation
Salesforce API sessions expire or become invalid when reused incorrectly or when IP relaxations are misconfigured.
Root Cause(s)
1. Expired OAuth token
2. Incorrect login endpoint
3. IP restriction mismatch
Step-by-Step Solution
1. Re-authenticate using OAuth refresh token
2. Verify correct login URL (
loginvstest)3. Check Connected App policies
Edge Cases & Variations
1. Sandbox tokens don’t work in production
2. JWT flows require correct certificate setup
Common Mistakes to Avoid
1. Hardcoding session IDs
See less2. Mixing sandbox and prod credentials