Ask Ken Adams a questionLost your password? Please enter your email address. You will receive a link and will create a new password via email.
Ask Ken Adams a questionPlease 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 does my Apex test class fail with “Mixed DML Operation” error?
You’re modifying setup and non-setup objects in the same transaction. Problem Explanation Salesforce separates setup objects (User, Profile) from standard objects to maintain system integrity. Root Cause(s) 1. Creating Users and Accounts together 2. Updating Permission Sets alongside data records 3.Read more
You’re modifying setup and non-setup objects in the same transaction.
Problem Explanation
Salesforce separates setup objects (User, Profile) from standard objects to maintain system integrity.
Root Cause(s)
1. Creating Users and Accounts together
2. Updating Permission Sets alongside data records
3. Test setup not isolated
Step-by-Step Solution
1. Move setup object DML to
System.runAs()2. Separate transactions using
@testSetup3. Use async Apex for one side if required
Edge Cases & Variations
1. Permission Set Assignments count as setup DML
2. Community Users increase complexity
Common Mistakes to Avoid
1. Creating users inside main test method
2. Ignoring setup vs non-setup distinction
See lessWhy does my validation rule fail during data migration?
Validation rules apply during imports unless bypassed. Problem Explanation Data Loader, APIs, and integrations enforce validation rules just like UI operations. Root Cause(s) 1. No bypass condition 2. Required fields missing in import 3. Incorrect formula logic Step-by-Step Solution 1. Add custom peRead more
Validation rules apply during imports unless bypassed.
Problem Explanation
Data Loader, APIs, and integrations enforce validation rules just like UI operations.
Root Cause(s)
1. No bypass condition
2. Required fields missing in import
3. Incorrect formula logic
Step-by-Step Solution
1. Add custom permission bypass
2. Assign permission to integration user
3. Update validation rule condition
Edge Cases & Variations
1. Bulk API behaves same as UI
2. Managed rules cannot be bypassed
Common Mistakes to Avoid
1. Disabling rules permanently
2. Using profile-based checks
See lessWhy does my Salesforce test class pass locally but fail in CI deployment?
The target org has different data, settings, or automation. Problem Explanation CI environments expose hidden dependencies and stricter validations. Root Cause(s) 1. Hardcoded IDs 2. Missing test data 3. Environment-specific automation Step-by-Step Solution 1. Remove hardcoded references 2. Create cRead more
The target org has different data, settings, or automation.
Problem Explanation
CI environments expose hidden dependencies and stricter validations.
Root Cause(s)
1. Hardcoded IDs
2. Missing test data
3. Environment-specific automation
Step-by-Step Solution
1. Remove hardcoded references
2. Create complete test data
3. Disable conflicting automation if needed
Edge Cases & Variations
1. Sandboxes differ from production
2. Feature flags affect behavior
Common Mistakes to Avoid
1. Relying on org configuration
2. Ignoring CI logs
See lessWhy does my Salesforce REST API return 403 Forbidden?
The connected app or user lacks required permissions. Problem Explanation Salesforce enforces OAuth scopes, object access, and IP restrictions on API calls. Root Cause(s) 1. Missing API Enabled permission 2. Insufficient OAuth scopes 3. IP relaxation not configured Step-by-Step Solution 1. Verify usRead more
The connected app or user lacks required permissions.
Problem Explanation
Salesforce enforces OAuth scopes, object access, and IP restrictions on API calls.
Root Cause(s)
1. Missing API Enabled permission
2. Insufficient OAuth scopes
3. IP relaxation not configured
Step-by-Step Solution
1. Verify user profile permissions
2. Check Connected App OAuth scopes
3. Review IP relaxation settings
Edge Cases & Variations
1. Community users have limited API access
2. Named Credentials simplify auth issues
Common Mistakes to Avoid
1. Using wrong user for integration
2. Ignoring permission sets
See lessHow do I deploy Apex triggers without failing test coverage?
Write focused test classes that cover all trigger paths. Problem Explanation Salesforce requires 75% overall coverage and trigger execution during deployment. Root Cause(s) 1. Missing test data 2. Trigger logic depends on existing records 3. Unhandled branches Step-by-Step Solution 1. Create test daRead more
Write focused test classes that cover all trigger paths.
Problem Explanation
Salesforce requires 75% overall coverage and trigger execution during deployment.
Root Cause(s)
1. Missing test data
2. Trigger logic depends on existing records
3. Unhandled branches
Step-by-Step Solution
1. Create test data inside
@testSetup2. Cover insert, update, delete scenarios
3. Assert outcomes
Edge Cases & Variations
1. Flow-triggered logic also needs coverage
2. SeeAllData=false may hide dependencies
Common Mistakes to Avoid
1. Relying on org data
2. Ignoring negative test cases
See lessWhy does my LWC show “Cannot read properties of undefined” when loading data?
The JavaScript tries to access data before the wire or API response is available. Problem Explanation LWCs render before async data arrives. Accessing nested fields without checks causes runtime errors. Root Cause(s) 1. Missing null checks 2. Incorrect API response shape 3. Wire method not returningRead more
The JavaScript tries to access data before the wire or API response is available.
Problem Explanation
LWCs render before async data arrives. Accessing nested fields without checks causes runtime errors.
Root Cause(s)
1. Missing null checks
2. Incorrect API response shape
3. Wire method not returning expected fields
Step-by-Step Solution
1. Use optional chaining (
?.)2. Guard rendering with
if:true3. Log the response structure in
wiredResultget accountName() {
return this.accountData?.Name;
}
Edge Cases & Variations
1. Imperative Apex calls need manual loading states
2. Cacheable Apex may return stale data
Common Mistakes to Avoid
1. Assuming data exists on first render
2. Accessing nested objects blindly
See less