Account Attributes

Feedback Documentation Feedback Connectivity Documentation Feedback
1

The following lists the account attributes:

The user’s preferred name

This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/connectors/saas/bamboohr/help/saas_connectivity/bamboohr/account_attributes.html
2

Please consider the following updates to this documentation:

  • middleName is an account attribute provided OOTB by the connector as well, but is not listed in the documentation.
  • It is worth noting in the documentation (until it can be fixed, hopefully), that all of these attributes including the 3 at the bottom that are not in the schema ootb (birthdate, homeEmail, and bestEmail) are brought into SailPoint even if they are not listed in the account schema. They won’t be visible in the UI, but the data is visible via the APIs.
  • It is worth nothing in the documentation (until it can be enhanced, hopefully) that you cannot add attributes to this connector even if they exist in the system and are available via the API being used. The connector will not error, but it will not bring in any attributes outside of the list currently documented (+ middleName that is not documented, but does come in). For example, OOTB all address fields are brought in, but zipcode is not one of them. Adding zipcode to the account schema does not, however, bring in zipcode.
5

Hi Jill! Thank you for your input. We’ve created a Jira issue to track the effort and we’ll update the comment thread when it’s been addressed: Jira

6

Hi @jroozeboom, the following updates have been made.

  • middleName not listed: middleName added in account attributes section.
  • Attributes brought into SailPoint even if they are not listed in the account schema: This has been fixed at the connector level now. Going forward we are aggregating the attributes present in the account schema. These three attributes (birthdate, homeEmail, and bestEmail) have been removed from the guide.
  • Cannot add attributes to this connector even if they exist in the system. This has been fixed. If an attribute is added to the account schema, it will get aggregated in the source.