and more in a single search tool across platforms. Read the announcement here. |
12/13/2023 02:59 AM
Hello Team,
We have a new Salesforce instance connection, which was successful, however, the import jobs are getting an error. This job has been successful few times but most of the times it has been errored.
Below is the logs for the job:
JOB ATTRIBUTE NAME JOB ATTRIBUTE VALUE
Job Name | Application Data Import (Single Threaded) |
Job Type | full |
Import Type | accounts |
Error in checkBatchState | InvalidBatch : Failed to process query: INVALID_FIELD: FederationIdentifier, UserPermissionsSupportUser,Fortive_ID__c,UserPermissionsOfflineUser ^ ERROR at Row:1:Column:311 No such column 'Fortive_ID__c' on entity 'User'. 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. |
Error in getResultId | null |
Existing Accounts | 1486 |
Accounts Retrieved From SalesForce | 0 |
New Account Added | 0 |
Existing Account Updated | 0 |
Accounts Activated | 0 |
Accounts Inactivated | 0 |
FeatureLicense Inserted | 0 |
FeatureLicense Updated | 5 |
FeatureLicense Account Entitlements1 Mapping deleted | 0 |
FeatureLicense Inactivated | 5 |
Attached details from log viewer.
Kindly check and let me know the issue.
Regards,
Vidhi.
Solved! Go to Solution.
12/14/2023 09:06 AM
Hi @Vidhimehta
Thanks for reaching out to Saviynt Forums regarding the mentioned issue.
This is a known issue and documented in the Saviynt documentation. Please refer Troubleshooting (saviyntcloud.com)
Import Fails with the INVALID FIELD Exception The following error message is displayed in the debug log file: Error - Failed InvalidBatch : Failed to process query: INVALID_FIELD: UserPermissionsSupportUser , UserPermissionsOfflineUser,UserPermissionsSiteforcePublisherUser ERROR at Row:1:Column:338 No suc h column 'UserPermissionsSiteforcePublisherUser' on entity 'User'. 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.
Cause: Batch Id from the Salesforce Bulk API is not processed because the FEATURE_LICENSE_JSON connection parameter has additional attributes that are not supported or do not have access to the required Salesforce objects.
Resolution: Ensure that the user's API call is working from Postman. Use the failed query to make the Postman call, remove the attributes not supported or specified multiple times, and check the value specified in the FEATURE_LICENSE_JSON parameter.
Regards,
Dhruv Sharma