Social Posts ending up in error queue due to content version error.
Last updated 2018-07-18 ·Reference W-4385708 ·Reported By 1 users
If you use Social Customer Service and your ORG has recently been updated to the 210 version of Salesforce you may notice that some of your Social Posts that have attachments (Images, Videos, etc.) end up in the error queue.
The error you are going to see will contain this line:
InboundSocialPostHandlerImpl at line 446, column 1: Insert failed. First exception on row 0; first error: INVALID_FIELD_FOR_INSERT_UPDATE, ContentVersion: bad field names on insert/update call: ContentLocation: [ContentLocation]
If you run into this issue, you will have to open a case with support to have a permission enabled that will allow Social Customer Service to process these files and prevent Social Posts from building up in your error queue.
1. Send a Social Post containing an Image or Attachment to your Org.
2. Navigate to the Social Customer Service Error queue.
3. Notice Social Post with Error stating content version permission issues.
There is no work around at this stage as this will require a permission to be enabled on your Salesforce Org.
Reported By (1)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.