Error 15
At Row:1:Column:49, No such column 'xxx' on entity 'yyy'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name
When data is bulk-loaded on the Salesforce side, a callback Platform Event is created and real-time sync to Service Board is triggered. In cases where the profile of the Service Board integration user does not have permissions to access the fields listed in the SOQL payload for the Platform Event, a failed HTTP Notification with the name Notification for Fetch Callback Event Data Request is generated.
Sample Response Body
[{"message":"\nCurrencyIsoCode,OwnerId,Name,ParentId,SVMXC__Preferred_Technician__c,CreatedDate\n ^\nERROR at Row:1:Column:49\nNo such column 'SVMXC__Preferred_Technician__c' on entity 'Account'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.","errorCode":"INVALID_FIELD"}]
To address this error for fields needed by Service Board:
1. In Salesforce, on the Setup page, in the left pane, in the Platform Tools section, under Objects and Fields, click Object Manager, and then in the list view, click to open the record with a Label field value that matches the 'yyy' value in the error message.
2. On the record page, in the left pane, click Fields & Relationships, and then in the right pane, in the list view, click the field with a name that matches the 'xxx' value in the error message.
3. On the field record page, click Set Field-Level Security, and then in the list view, select the profile for the Service Board Integration user.
4. If needed, select the Visible check box for the profile, and then in Service Board, retry the failed HTTP Notifications.
To address this error for fields not needed by Service Board:
1. In Salesforce, on the Setup page, in the left pane, in the Platform Tools section, under Objects and Fields, click Object Manager, and then in the list view, click to open the record with a Label field value that matches the 'yyy' value in the error message.
2. On the record page, in the left pane, click Field Sets, and then in the right pane, in the list view, click to open the Field Set record for Service Board real-time sync that includes the unnecessary fields.
3. On the In the Field Set page, remove the unnecessary fields, and then save your changes.
4. In Max Admin, on the System Management (
) launchpad menu, click HTTP Notifications, and then in the list view, open a relevant failed Notification for Fetch Callback Event Data Request notification.
) launchpad menu, click HTTP Notifications, and then in the list view, open a relevant failed Notification for Fetch Callback Event Data Request notification.5. In the top right corner, on the Options (
) menu, click Resolve Failed HTTP Notification to clear the Processing Data field value that had the permission issue and retry the notification, and then if needed, open and resolve any additional failed HTTP Notifications.
) menu, click Resolve Failed HTTP Notification to clear the Processing Data field value that had the permission issue and retry the notification, and then if needed, open and resolve any additional failed HTTP Notifications. | • At times when two fields in a record have permission issues, only one field is reported in the related HTTP Notification each time real-time sync runs. In these cases, when the Resolve Failed HTTP Notifications option is invoked, Failure status is not cleared and a different field appears in the notification. To reach resolution, the option must be invoked a second time. • The Resolve Failed HTTP Notification option on the Options menu is available only in failed HTTP Notifications with a Related HTTP Notification Request field value of Fetch Callback Data Request and a Response Body field value that includes "errorCode":"INVALID_FIELD". |