# Troubleshooting

If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

- [SailPoint Identity Services Documentation](<https://documentation.sailpoint.com/saas/help/index.html>)
- [SailPoint Support Knowledge Base](<https://support.sailpoint.com/csm?id=kb_view2&amp;kb_id=05ff44289f011200550bf7b6077fcfa3>)
- [SailPoint Developer Community](<https://developer.sailpoint.com/>)

## Connector Not Reading Additional Attribute Value

**Issue**: The connector does not read additional attribute values even though the API returns the value.

**Resolution**: Add the following entry key with the path for the attribute as shown in the example below:

```xml
<entry key="jsonPathMapping">
  <value>
    <Map>
      <entry key="approvalLimit" value="['urn:ietf:params:scim:schemas:extension:sap:ariba:2.0:User'].approvalLimit"/>
    </Map>
  </value>
</entry>
```

## Only One User Is Displayed After Aggregation

**Issue**: Previously created duplicate users (with different letter case) are present in a realm, however, when creating a new user only one user is showing after aggregation. This happens when an ID is already present (irrespective of the letter case) in Ariba realms.

**Resolution**: Ensure user values are unique. The SailPoint platform supports unique identities irrespective of the letter case.

## User `xxxxxxxxx` Already Exists Either as Enterprise or a Third Party User Error

**Issue**: The following error is displayed: User `xxxxxxxxx` already exists either as Enterprise or a Third Party user.

**Resolution**: Ensure user values are unique. The SailPoint platform supports unique identities irrespective of the letter case.