Insufficient Access or Invalid Fields

The INSUFFICIENT_ACCESS_OR_READONLY and INVALID_FIELD_FOR_INSERT_UPDATE errors occurs when Revenue.io attempts to write data to Salesforce records that have restricted permissions or are set to "Read Only." Due to these security settings, Salesforce blocks the update operation, preventing Revenue.io activities or updates from being properly logged.

Common Causes

This error typically stems from field-level security configurations in your Salesforce org:

• Field-level security settings that restrict write access to fields Revenue.io needs to update
• Permission sets or profiles lacking the necessary "Edit" permissions for relevant fields
• Fields marked as "Read Only" in the field-level security settings

Troubleshooting Steps

Step 1: Verify the "RingDNA Agent for Salesforce" Permission Set

First, ensure all Revenue.io users have the required permission set:

1. Navigate to Setup in your Salesforce instance
2. Go to Users → Permission Sets
3. Find the RingDNA Agent for Salesforce permission set
4. Click on Manage Assignments
5. Verify that all users experiencing the error have this permission set assigned
6. If users are missing this permission set, click Add Assignments and select the appropriate users
7. Click Assign and Done

Step 2: Identify the affected fields

If users still experience errors after verifying permission set assignments, determine which specific fields are causing the error. Common fields include:

• Activity-related fields (TaskSubtype, Status, etc.)
• Custom fields created for Revenue.io integration
• Fields on standard objects that Revenue.io needs to modify

Step 3: Check field-level security settings for Standard Fields

Follow these steps to verify the current field-level security settings:

1. Navigate to Setup in your Salesforce instance
2. Go to Object Manager
3. Select the object containing the fields in question (usually Task, Event, or custom objects)
4. Click Fields & Relationships
5. Select the field that needs to be updated
6. Click Set Field-Level Security
7. Check which profiles or permission sets currently have "Read Only" access instead of "Edit" access

Best Practices

• Only grant the minimum necessary permissions required for Revenue.io functionality. This is referred to as the principle of least privilege.
• Rather than modifying profiles directly, use permission sets for more granular and manageable control

Need Additional Help?

If you continue to experience errors after implementing these changes:

• Review your Revenue.io logs to identify specific fields causing the error
• Contact Revenue.io Support with details about the specific error messages and steps you've taken
• Consider engaging your Salesforce administrator to perform a comprehensive review of your security settings