Salesforce Sync Error: Invalid or Null for Restricted Picklist

Grace Wannapongsai
Grace Wannapongsai
  • Updated

Summary

This article explains why you may see [INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST] error in the Riva Cloud sync log when syncing to Salesforce, typically when Riva attempts to write a value that is not allowed for a restricted picklist field.

Symptoms / Issue

When encountering this error, users may experience:

  • Sync fails when Riva attempts to update a record in Salesforce.

  • Error message:

    Error – [INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST] Sub Type: bad value for restricted picklist field: Feedback –Sub_Type__c: Test Email – RIVA values check

  • Other examples of this error pattern include fields such as Meeting_Purpose__c, Activity_Type__c, Purpose_of_Visit__c, RPS_Activity_Type__c, FRB_Case_Type__c, and others. 

Environment: CRM activity/calendar sync (Salesforce)

Cause of the Issue

Riva attempted to sync a value to Salesforce field (e.g.,Sub_Type__c), but Salesforce rejected the update because the field is configured as a restricted picklist and the value being sent is not one of the valid allowed options.

There are three common contributing causes:

  1. Invalid or mismatched value: The value Riva is attempting to write does not match any of the valid picklist options in Salesforce (e.g., a spelling difference, a value that was renamed, or a value selected in Insight that does not exist in the target environment).
  2. Field-level security / permissions: The error can also occur when the Riva service account or the affected user does not have access to the picklist value, even if the value itself is valid. Importantly, the error message does not distinguish between an invalid value and a permissions issue — both return the same error.
  3. Recent changes to Salesforce picklist configuration: If the error is new and sync was previously working, someone may have recently modified the picklist in Salesforce — for example, removing, renaming, or restricting a value that was previously valid.

Resolution / Steps

  1. Identify the field and value from the sync log

    Review the sync log error to identify:

    • The field API name (e.g., Sub_Type__c)
    • The value Riva attempted to write (e.g., Feedback)
    • The item that failed (e.g., the subject of the meeting or email)
  2. Review valid picklist options in Salesforce
    • In Salesforce, navigate to the field definition and confirm which values are currently valid and allowed for the restricted picklist.
  3. Check field-level security
    • If the error is new and sync was previously working, verify whether someone recently modified the picklist in Salesforce (e.g., added, removed, or renamed values). Reverting or correcting the change in Salesforce may resolve the error.
  4. Update the configuration
    • Once the valid values are confirmed, update the Riva configuration or the values being mapped so that Riva syncs only valid, accessible picklist values to Salesforce.