Creating External Credentials for enosix Sync

When using external credentials in Salesforce, user receives an error when attempting to set up/execute an enosix sync. This issue can happen when either the automated process user or the executing user does not have correct permissions.

System.CalloutException: We couldn't access the credential(s). You might not have the required permissions, or the external credential "SAP_CREDENTIAL" might not exist.

Below is the step by step guide on how to successfully configure the applications.

Setup: Named Credentials

1. Select External Credentials tab and create New External Credential by providing:
   • Label
   • Name
   • Authentication Protocol = Basic Authentication.
2. Create New Principal by providing:
   • Parameter Name
   • Sequence Number (in case you have more than one Principal and one has to be prioritized over the other)
   • Identity Type (whether you are going to have a singe login or multiple logins). In the example Named Principal Identity Type is used.
3. Go back to Named Credentials tab and create a new named credential (do not create a legacy named credential):
   • Label
   • Name
   • URL (proxy)
   • Enabled for Callouts (yes)
   • External Credential: Select the external credential you created in step 1
   • Generate Authorization Header (yes)
   • Allowed Namespaces for Callouts : ensxsync, ensxapp, ensxsdk

Setup: Permission Sets

1. Create a New Permission Set by providing
   • Label = enosix External Credentials
2. Under the Apps section of enosix External Credentials permission set click on Object Settings.
3. From the list of objects select User External Credentials
4. Edit the permissions by granting READ access.
5. Under the Apps section of enosix External Credentials permission set click on External Credential Principal Access
6. Enable earlier created Principal
7. Assign enosix External Credentials permission set to your user.

Assign Permission Set to Automated Process User

The Automated Process user is a built-in behind-the-scenes user that exists in every single org. It is invisible to Setup > Users, but it can be viewed if queried:

SELECT Id, Name, UserType, ProfileId FROM User WHERE UserType = 'AutomatedProcess'

1. Use this query to find the Automated Process user

2. Get the User Id and associate it with a Permission Set (or Permission Set Group, so you can use Setup to add multiple Permission Sets to it).

3. Associate the permission set with the user using an INSERT statement from the Salesforce.

4. Open Developer Console

5. Select Debug

6. Click Open Execute Anonymous Window

   Example: code, make sure you update values accordingly

// for a Permission Set Group
                  Id myPermissionSeGrouptId = [SELECT Id FROM PermissionSetGroup WHERE DeveloperName = 'your_Permission_Set_Group_API_Name'].Id;
 
                  List<User> userList = [SELECT Id FROM User WHERE UserType = 'AutomatedProcess'];
                  for (User u : userList) {
                        INSERT new PermissionSetAssignment(
                              AssigneeId = U.ID - Unique Digital Identity ,
                              PermissionSetGroupId = myPermissionSeGrouptId
                        );
                  }

 // for a Permission Set
                  Id myPermissionSetId = [SELECT Id FROM PermissionSet WHERE name = 'your_Permission_Set_API_Name'].Id;
 
                  List<User> userList = [SELECT Id FROM User WHERE UserType = 'AutomatedProcess'];
                  for (User u : userList) {
                        INSERT new PermissionSetAssignment(
                              AssigneeId = U.ID - Unique Digital Identity ,
                              PermissionSetId  = myPermissionSetId
                        );
                  }

Validation Rules

For any Validation Rule that needs to be bypassed by enosix Sync that isn’t controlled by a Permission Set, add the following exclusion to the validation rule:

TEXT($User.UserType) <> 'AutomatedProcess'

warning

If the code throws this error: Error System.DmlException: Insert failed. First exception on row 0; first error: TABSET_LIMIT_EXCEEDED, Can't complete this operation because you reached the limit of 0 custom tabs for Automated Process for the Automated Process user license.

Then follow the directions here Unable to Assign Permission Set to Automated Process User to delete the Knowledge tab from the org.