# SailPoint Ceridian Dayforce HCM Connector Documentation > Ceridian Dayforce HCM Connector Documentation # Documentation # Connecting SailPoint and Ceridian Dayforce HCM To connect SailPoint with Ceridian Dayforce HCM, perform the following tasks: ## Adding the Source in SailPoint To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs. > [!IMPORTANT] > > By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration. **To configure a new source:** 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Configure**. 5. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 6. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters. 7. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](). 8. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 9. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](). 10. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## Base Configuration Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary. 1. Enter a unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 6. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default. - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system. - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source. 7. Select **Save**. ## Connection Settings The following information is required to connect and interact with Ceridian Dayforce HCM. **Basic Authentication Screenshot** > [!NOTE] > > **Screenshot** > > [![Basic Authentication Screenshot]()]() **Token Based Authorization Screenshot** > [!NOTE] > > **Screenshot** > > [![Token Based Authorization Screenshot]()]() 1. Enter the Base URL or Generic Base URL for the Ceridian Dayforce HCM source. For example: - Base URL: `https://.dayforcehcm.com/api` - Generic Base URL: - `https://www.dayforcehcm.com/api` (Production) - `https://test.dayforcehcm.com/api` (Sandbox) > **Note** > > When you use a Generic Base URL, the connector automatically resolves it to the correct versioned endpoint. You do not need to update the URL when Dayforce changes hostnames. 2. Select an **Authentication Method**. You can select **Basic** or **Token Based Authentication**. If you select Token Based Authentication for your authentication method. Enter the **Dayforce Identity Server URL** that is used to retrieve the authentication token from the Ceridian Dayforce identity servers. 3. Enter the **Username** and **Password** of the Ceridian Dayforce service user dedicated to web service calls. 4. Enter the **Client Name** that uniquely identifies the client's Ceridian Dayforce instance. 5. Select **Save**. ## Aggregation Settings Provide the information the source uses to manage and filter Ceridian Dayforce HCM employees. For more information about aggregation, refer to [Loading Account Data](). > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() ### Aggregate Employee Statuses By default, the connector only aggregates Active employees. You can add additional custom employee status values to include in account aggregation processes. To add additional custom employee statuses in account aggregation: 1. In the **Aggregate Employee Statuses** field, enter the name of a custom employee status. > **Important** > > The **Active** status is the default aggregation status. It should not be removed. 2. Press Enter on your keyboard to add the employee status name to a growing list. 3. Select **Save**. ### Aggregate Terminated Employees You can include terminated employees within a defined time period to account aggregation processes. To include terminated employees and configure the time period: 1. Enable **Aggregate Terminated Employees** to include terminated employees in account aggregation processes. 2. In the **Past Termination Offset in Days** field that displays, enter the number of days in the past you want to aggregate terminated employees. You can also enter a specific date range. > **Note** > > If the **Past Termination Offset in Days** field entry is null, the connector aggregates all terminated employees. 3. Select **Save**. ### Aggregate Inactive Employees Enable **Aggregate Inactive Employees** to include inactive employees in account aggregation processes. ### Aggregate Prestart Employees Enable **Aggregate Prestart Employees** to include employees whose Employment Status is `Prestart` in account aggregation processes. ### Configure Account Aggregation Filters Define the scope of accounts to aggregate based on query parameters. To configure account aggregation filters: 1. In the **Account Aggregation Filters** field, enter a **Field Name** and an associated **Field Value**. For example: **Field Name**: `filterOriginalHireStartDatea` **Field Value**: `2017-01-01T13:24:56` 2. Press Enter on your keyboard to add the filter to the rolling list of account aggregation filters. Repeat as necessary for additional account aggregation filters. 3. Select **Save**. ### Define Employee Statuses for Enabled Accounts Define the account statuses that indicate which employee accounts are enabled in the managed system. To define enabled employee account statuses: 1. In the **Enabled Employee Statuses** field, enter the name of an account status which indicates that the employee account is enabled. > **Important** > > The **Active** status is the default enabled account status. It should not be removed. 2. Press Enter on your keyboard to added the status to a growing list. 3. Select **Save**. ### Aggregate Primary Employment Enable **Aggregate Primary Employment** to include the primary employment attributes in employee aggregation. If this option is disabled, the source aggregates the most recent employment attributes. ### Delta Aggregation Enable **Delta Aggregation** to aggregate new accounts or accounts that have changed since the last aggregation. ## Connector Configuration Attributes Use the following source configuration attributes when you manage the Ceridian Dayforce HCM connector. ### `attributeMapping` Use this attribute to map additional attributes from `EmployeeProperties`. - **Key:** The SailPoint schema attribute name. - **Value:** The JSON path in `EmployeeProperties`. **Example:** ```json "attributeMapping": { "Long Term Absence": "EmployeeProperties.Items[3].BitValue", "Microsoft License": "EmployeeProperties.Items[4].OptionValue.ShortName" } ``` ### `numericMappedAttributesAsString` Use this attribute to list attribute names. - **Purpose:** Avoid type-cast errors when a target attribute is numeric but should be treated as a string during aggregation. - **Behavior:** The connector converts each listed custom attribute to a string. **Example:** `numericMappedAttributesAsString: ['xxNormalWeeklyHours', 'attributeName2']` ## Provisioning Settings Configure optional settings related to provisioning operations. The configurations made in the provisioning settings tab apply to all provisioning operations. The provisioning tab provides options for you to enter the API country code settings. For information on the available provisioning policy attributes, refer to [Provisioning](). > [!NOTE] > > **Screenshot** > > [![Provisioning Settings]()]() To configure provisioning settings, complete the following: 1. Enter the **Business Phone Country Code** as required to update the employees' phone details. For example, enter `CAN` for Canada or `IND` for India. The default country code configured is `USA`. 2. Select **Save**. ## Additional Settings Configure additional settings related to connector operations. ### Retry Configuration Configure how the connector retries failed aggregation events. You can specify which error messages will prompt a retry, and then limit the number of times the connector should retry an operation before terminating it. > [!NOTE] > > **Screenshot** > > [![Additional Settings]()]() > [!NOTE] > > **Screenshot** > > [![Additional Settings]()]() To configure operation retries: 1. In the **Retry Error List** field, specify the errors which should prompt the connector to retry a failed aggregation process. Press Enter to add the errors to a growing list. For example, you can enter `Internal Server Error`. By default, the connector retries the following errors (defined by the `defaultRetryList` parameter): - `Bad Gateway` - `Service Unavailable` - `Gateway Timeout` - `socket hang up` - `ECONNRESET` - `TimeoutError` - `ConnectionRefusedError` - `connection timeouts` 2. In the **Maximum Number of Retries** field, specify the maximum number of times the system should retry aggregation processes before terminating the process. You can enter from `0` to `10`. The default value is `3`. 3. In the **Delay Between Retry Attempts in Seconds** field, enter the duration of time the connector waits between retry attempts. You can enter from `0` to `10` seconds. The default value is `2`. 4. Select **Save**. ## Review and Test Perform a test to confirm the connection to SailPoint. 1. Go to **Review and Test**. 2. Confirm that the entries in each field are correct. If you note any mistakes, return to the section and make corrections. 3. Select **Test Connection**. ## SailPoint Application Onboarding SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface. For more information, refer to [Application Onboarding]() in the SailPoint SaaS documentation. # Integrating SailPoint with Ceridian Dayforce HCM SailPoint's Ceridian Dayforce HCM connector provides the capability for seamless and secure connection to Dayforce HCM, which is used as an authoritative source and acts as a source of employee records. This guide is designed to give specific information about the requirements and field definitions needed to get a working instance of a Ceridian Dayforce HCM source. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The SailPoint Ceridian Dayforce HCM connector supports the following features: - Account Management - Full Account Aggregation - Delta aggregation for employees - Single Account Aggregation - Update account provisioning (limited attributes) - Concurrent Employment (Primary or Secondary) ## Prerequisites Before configuring the Ceridian Dayforce HCM connector, be sure you complete certain tasks or have acquired specific information. - You must know the Ceridian Dayforce HCM client namespace. ## Required Permissions You must configure the service account with certain permissions to run a test connection and aggregate or provision data. ### Account Aggregation: Default Attributes There are specific permissions required to aggregate the default account attributes. You may also need to enable certain security features or grant additional field-level access. The following table lists the default account attributes and the associated permissions and security considerations required to aggregate them. Attributes with similar requirements are grouped together where possible.
Attributes Required Permission Security Considerations

Employee XRefCode

Employee Number

Eligible For Rehire

CommonName

HomeOrganization

Federated Id

Hire Date

New Hire Approved

New Hire Approval Date

New Hire Approved By

Original Hire Date

Start Date

Pre Start Date

Login Id

Display Name

First Name

Last Name

Employee Termination Date

The user role must have access to the Read Data subfeature.

To find the Read Data subfeature, go to System Admin > Roles > Features > HCM Anywhere > Web Services.

Enable XRefCode

To enable XRefCode, go to: System Admin > Roles > Web Services Field-Level Access > RESTful Services > Human Resources > Employee.

Employment Status

EmployeeEmploymentStatus (and relevant child nodes)

To enable this feature, go to System Admin > Roles > Web Services Field-Level Access > RESTful Services > Human Resources.

Enable read access for Employee Status Information.

To grant this field-level access, go to System Admin > Roles > Authorizations.

Employment Type

Employment Type

EmployeeEmploymentType (and relevant child nodes)

To enable this feature, go to System Admin > Roles > Web Services Field-Level Access > RESTful Services > Human Resources.

Business Email

PersonContact (and relevant child nodes)

To enable this feature, go to System Admin > Roles > Web Services Field-Level Access > RESTful Services > Human Resources.

Enable read access for Employee Contact Information - Personal and/or Employee Contact Information - Business.

To grant this field-level access, go to System Admin > Roles > Authorizations.

Business Phone

Business Phone Country Code

Location

EmployeeWorkAssignment (and relevant child nodes)

To enable this feature, go to System Admin > Roles > Web Services Field-Level Access > RESTful Services > Human Resources.

Enable read access for Employee Work Assignment - Primary Records .

To grant this field-level access, go to System Admin > Roles > Authorizations.

Position

Work Location

Department

Job XRefCode

Job Name

JobRank

Job EmployeeEEO

Job Classification

Job FLSAStatus

Manager XRefCode

EmployeeManager (and relevant child nodes)

To enable this feature, go to System Admin > Roles > Web Services Field-Level Access > RESTful Services > Human Resources.

None

Manager FirstName

Manager LastName

Role XRefCode

EmployeeRole (and relevant child nodes)

To enable this feature, go to System Admin > Roles > Web Services Field-Level Access > RESTful Services > Human Resources.

Enable read access for Employee Profile - Security Settings - Roles.

To grant this field-level access, go to System Admin > Roles > Authorizations.

Role Name

Organization Unit Name
### Account Aggregation: Additional Attributes There are specific permissions required to aggregate additional account attributes. You may also need to enable certain security features or grant additional field-level access. The following table lists additional account attributes and the associated permissions and security considerations required to aggregate them. Attributes with similar requirements are grouped together where possible.
Attribute Required Permission Security Considerations

BirthDate

The user role must have access to the Read Data subfeature.

To find the Read Data subfeature, go to System Admin > Roles > Features > HCM Anywhere > Web Services.

Enable XRefCode

To enable XRefCode, go to: System Admin > Roles > Web Services Field-Level Access > RESTful Services > Human Resources > Employee.

BioExempt

Gender

MaritalStatus

EmployeeMaritalStatus (and relevant child nodes)

Grant read access for Employee Personal Information

To grant this field-level access, go to System Admin > Roles > Authorizations.

Address

PersonAddress (and relevant child nodes)

Grant read access for Employee Contact Information

To grant this field-level access, go to System Admin > Roles > Authorizations.

City

PostalCode

Country

State
### Provisioning There are specific permissions required to provision certain account attributes. You will also need to enable certain security features. The following table lists account attributes and the associated permissions and security considerations required to provision them. Attributes with similar requirements are grouped together where possible.
Attribute Required Permission Security Considerations

FirstName

The user role have access to the PATCH/POST Employee HR Data subfeature under HCM Anywhere > Web Services in the Features tab of System Admin > Roles.

To find the PATCH/POST Employee HR Data subfeature, go to System Admin > Roles > Features > HCM Anywhere > Web Services.

Enable Can Create and Can Update

To enable these features, go to System Admin > Roles > Authorizations.

LastName

BusinessEmail

The user role have access to the PATCH/POST Employee HR Data subfeature under HCM Anywhere > Web Services in the Features tab of System Admin > Roles.

To find the PATCH/POST Employee HR Data subfeature, go to System Admin > Roles > Features > HCM Anywhere > Web Services.

Enable Can Create and Can Update

To enable these features for Employee Contact Information - Personal and/or Employee Contact Information - Business, go to System Admin > Roles > Authorizations.

BusinessPhone
# Provisioning The Ceridian Dayforce HCM connector supports provisioning, allowing you to create and manage accounts and entitlements in Ceridian Dayforce HCM directly from SailPoint. **Prerequisite:** Your system is configured for provisioning. When SailPoint provisions new accounts to the source, it uses the attributes on the **Create Account** page as instructions or a template for what to include in the account. This page is also referred to as the *provisioning policy*. When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment. For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account. > [!IMPORTANT] > > This section describes the default **Create Account** configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail. ## Default Create Account Attributes | Account Attribute | Generator | Description | | --- | --- | --- | | FirstName | Identity Attribute - First Name | The user's first name. | | LastName | Identity Attribute - Last Name | The user's last name. | | BusinessEmail | Identity Attribute - Work Email | The email address the user will use to sign in to Ceridian Dayforce. By default, the effective start date is system date. This can be edited by the Admin. | | BusinessPhone | Identity Attribute - Work Phone | The work phone of the user. By default, the business phone country is USA. This can be edited by the Admin with any value from Provisioning Settings. | # Schema Reference The application schema is used to configure the objects returned from a connector. > [!NOTE] > > - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas]() for more information. > - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified. The Ceridian Dayforce HCM connector uses the following default correlation and object configurations. ## Default Correlation Configuration Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements. You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities]() for more information. When you first create the Ceridian Dayforce HCM source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | Business Email | Equals | Work Email | | Employee Number | Equals | Employee Number | | Display Name | Equals | Name | ## Default Account Schema Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location. The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas]() for more information. ### Default Account ID SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*. > [!CAUTION] > > Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts. > > To resolve issues caused by changing account IDs, reconfigure them to their default values. The following table lists the default account IDs for this connector: | Account ID | Schema Object Type | | --- | --- | | Employee XRefCode | Account | ### Default Account Attributes The Ceridian Dayforce HCM connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.
Attribute Name Description
Employee XRefCode Reference code for the employee.
Technical Path: XRefCode
EmploymentStatusXRefCode Reference code for the employee's employment status. To aggregate the EmploymentStatusXRefCode attribute, you must add the customEmployee attribute to the source configuration using the SailPoint REST API. For example:
[
  {
    "op": "add",
    "path": "/connectorAttributes/customEmployeeStatus",
    "value": [
      "Leave_Of_Absence",
      "CROSS_BORDER",
      "Leave_Of_Absence_Paid"
    ]
  }
]

Note - For more information on SailPoint's REST APIs, refer to Best Practices: REST API Authentication and REST API - Update Source (Partial) in the SailPoint Developer Community.
Technical Path: EmploymentStatusXRefCode
Employee Number The account's employee number.
Technical Path: EmployeeNumber
Eligible For Rehire Indicates if the employee is eligible to be rehired; true or false.
Technical Path: EligibleForRehire
Common Name The employee's common name.
Technical Path: CommonName
Home Organization The employee's home organization.
Technical Path: HomeOrganization.LongName
Federated Id Unique identifier for the employee's SSO login information.
Technical Path: FederatedId
Hire Date Date that an employee was hired; may be a rehire date.
Technical Path: HireDate
New Hire Approved Indicates if a new hire has been approved for employment; true or false.
Technical Path: NewHireApproved
New Hire Approval Date Date that a new hire was approved.
Technical Path: NewHireApprovalDate
New Hire Approved By Indicates the source of the new hire's approval.
Technical Path: NewHireApprovedBy
Original Hire Date The employee's original start date.
Technical Path: OriginalHireDate
Start Date The employee's start date.
Technical Path: StartDate
Pre Start Date The date that the employee can access the Ceridian Dayforce application prior to their start date.
Technical Path: PreStartDate
Login ID The employee's login ID.
Technical Path: LoginId
Display Name The employee's display name.
Technical Path: DisplayName
First Name The employee's first name.
Technical Path: FirstName
Last Name The employee's last name.
Technical Path: LastName
Employee Termination Date The employee's termination date.
Technical Path: TerminationDate
Employment Status Lists the employee's employment status descriptions i.e. leave of absence, retired
Technical Path: EmploymentStatuses.Items[*].EmploymentStatus.XRefCode
Employment Type Designates if an employee is a contractor or a pensioner.
Technical Path: EmploymentTypes.Items[*].EmploymentType.XRefCode
Business Email The employee's business email address.
Technical Path: Contacts.Items[?(@.ContactInformationType.XRefCode =="BusinessEmail")].ElectronicAddress
Business Phone The employee's business phone number.
Technical Path: Contacts.Items[?(@.ContactInformationType.XRefCode =="BusinessPhone")].ContactNumber
Business Phone Country Code The country code for the employee's business phone number.
Technical Path: Contacts.Items[?(@.ContactInformationType.XRefCode =="BusinessPhone")].Country.XRefCode
Location The employee's location.
Technical Path: Locations.Items[?(@.IsPrimary ==true)].Location.ShortName
Position The employee's position. By default, WorkAssignments details of location are marked as primary.
Technical Path when Aggregate Primary Employment is unchecked: WorkAssignments.Items.[0].Position.ShortName
Technical Path when Aggregate Primary Employment is checked: WorkAssignments.Items.[?(@.IsPrimary ==true)].Position.ShortName
Work Location The employee's work location.
Technical Path: WorkAssignments.Items.[0].Location.ShortName
Department The employee's department name, i.e. Accounting, Customer Service
Technical Path: WorkAssignments.Items.[0].Position.Department.LongName
Job XRefCode The Job's reference code.
Technical Path: WorkAssignments.Items.[0].Position.Job.XRefCode
Job Name The employee's job name.
Technical Path: WorkAssignments.Items.[0].Position.Job.ShortName
JobRank The employee's job rank.
Technical Path: WorkAssignments.Items.[0].Position.Job.JobRank
Job EmployeeEEO The employee's EEO category descriptions; i.e. Professional, Technician
Technical Path: WorkAssignments.Items.[0].Position.Job.EmployeeEEO.ShortName
Job Classification The employee's information on Job classifications; i.e. Sales, Marketing
Technical Path: WorkAssignments.Items.[0].Position.Job.JobClassification.ShortName
Job FLSAStatus Long name for a FLSA status; i.e. Exempt, non-exempt
Technical Path: WorkAssignments.Items.[0].Position.Job.FLSAStatus.XRefCode
Manager XRefCode The employee reference code of the employee's manager.
Technical Path: EmployeeManagers.Items[*].ManagerXRefCode
Manager FirstName The employee's manager's first name.
Technical Path: EmployeeManagers.Items[*].ManagerFirstName
Manager LastName The employee's manager's last name.
Technical Path: EmployeeManagers.Items[*].ManagerLastName
Role XRefCode The employee's Role reference code.
Technical Path: Roles.Items[*].Role.XRefCode
Role Name The employee's Role name.
Technical Path: Roles.Items[*].Role.ShortName
Organization Unit Name The name of the employee's Organization Unit.
Technical Path: OrgUnitInfos.Items[?(@.OrgUnitDetail.IsPrimary ==true)].OrgUnitDetail.ShortName
## Additional Customer Configurable Attributes The following additional attributes are available for the Ceridian Dayforce HCM source: | Attribute Name | Description | | --- | --- | | BirthDate | The employee's birthdate.
Technical Path: `BirthDate` | | BioExempt | Indicates if the employee is exempt from biological breaks; true or false.
Technical Path: `BioExempt` | | Gender | Identifies the employee's gender.
Technical Path: `Gender` | | MaritalStatus | Information on the employee's marital status code. This attribute links an employee and a marital status description. Use with the **Marital Status** entity to get employee marital status detail.
Technical Path: `MaritalStatuses.Items[0].MaritalStatus.XRefCode` | | Address | The employee's street address.
Technical Path: `Addresses.Items[0].Address1` | | City | The employee's city.
Technical Path: `Addresses.Items[0].City` | | State | The employee's state.
Technical Path: `Addresses.Items[0].State.XRefCode` | | PostalCode | The employee's postal code.
Technical Path: `Addresses.Items[0].PostalCode` | | Country | The employee's country.
Technical Path: `Addresses.Items[0].Country.XRefCode` | # 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]() - [SailPoint Support Knowledge Base]() - [SailPoint Developer Community]() ## Debug Logs For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings]().