Error during Access Import for Saleforce

[ARCrosthwaite]

We are seeing an error during the import of the Access import from Salesforce when the Role and/or Group entitlement types are added to the OBJECT_TO_BE_IMPORTED list.

When we run the access import when Role or Group are not included the import completes successfully. However, if either Role or Group are added to this list we see the following error in the the Job Log

InvalidBatch : Failed to process query: INVALID_FIELD: SystemModStamp, DeveloperName, PortalAccountId, PortalType from ^ ERROR at Row:1:Column:99 No such column 'PortalAccountId' on entity 'UserRole'. 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.

We've tried creating a fresh connection, a new endpoint, adding and removing mappings for these entitlement types. Each time the Group and Role types are removed the import works correctly but in every case when they are added the same error occurs.

Regs

Andrew C

[rushikeshvartak]

The error you are encountering during the Access import from Salesforce suggests that there is an issue with the query trying to access fields that do not exist on the UserRole object. The specific error message indicates that the field PortalAccountId does not exist on the UserRole entity.

Here are some steps you can take to resolve this issue:

Steps to Resolve:

1. Verify Field Names:

   • Check if the fields SystemModStamp, DeveloperName, PortalAccountId, and PortalType exist on the UserRole object in Salesforce.
   • If PortalAccountId is a custom field, ensure it is correctly named (e.g., PortalAccountId__c).

[ARCrosthwaite]

Yes @rushikeshvartak this would make sense however we've found that we are unable to solve the issue by controlling this. Saviynt documentation here suggests that only the Profile entitlement type attribute mapping can be changed.  We have however attempted to change the attribute mapping to both include and exclude PortalAccountId unfortunately this didn't solve the issue.  

Additionally to clarify PortalAccountId is not an entitlement type and is not included in the OBJECT_TO_BE_IMPORTED configuration where if you were importing a custom field you would place this.

Salesforce documentation here indicates that on the UserRole object the  PortalAccountId attribute is available and is not a custom attribute.  There is also the strange issue where even if we do not include the Role or UserRole entitlement types in the OBJECT_TO_BE_IMPORTED configuration and only include the Group object type (along with other object types which have proven to work correctly) we still  see the above error and always referencing the UserRole object even if we've specified only the Role object.

[rushikeshvartak]

Share logs