Start date or location field not syncing from Okta to 15Five

Ben Pemstein Ben Pemstein
· Updated

After a SCIM sync from Okta, the Start Date or Location field in 15Five shows blank even though the value exists in Okta. This article covers the two most common causes: incorrect attribute namespace and incorrect attribute mapping.

Diagnose

Check 1: Attribute namespace for Start Date → In Okta, open the 15Five app and go to Provisioning > Profile Editor. → Find the Start Date attribute and inspect its External namespace value. → If the namespace is anything other than urn:ietf:params:scim:schemas:extension:15Five:2.0:User → go to Fix 1. → If the namespace is correct → go to Check 2.

Check 2: Variable name for Start Date → In the Profile Editor, open the Start Date attribute. → Confirm the Variable Name is exactly startDate (case-sensitive). → If the variable name differs → go to Fix 1. → If the variable name is correct → go to Check 3.

Check 3: Mapping for Start Date → In the Profile Editor, click Mappings > Okta User to 15Five. → Find startDate and confirm it maps to a populated field on the Okta user profile. → If no mapping exists or the source field is empty → go to Fix 2. → If a mapping exists and the source field has data → contact 15Five Support (see escalation below).

Check 4: Location mapping formula → In Okta, go to Provisioning > To App > attribute mappings. → Find the Location attribute and inspect its mapped value. → If the value is not String.join(", ", user.city, user.state, user.countryCode) → go to Fix 3. → If the formula is correct, confirm user.city, user.state, and user.countryCode are populated on the Okta user profile. If any are empty, the location string will be incomplete or blank → go to Fix 3.

Fix

Fix 1 — Correct the Start Date attribute namespace or variable name

  1. In Okta, open the 15Five app.
  2. Navigate to Provisioning > Profile Editor.
  3. Click Add Attribute (or edit the existing Start Date attribute).
  4. Set Display Name to Start Date.
  5. Set Variable Name to startDate.
  6. Set External namespace to urn:ietf:params:scim:schemas:extension:15Five:2.0:User.
  7. Check User personal under Scope.
  8. Click Save.
  9. Trigger a sync for an affected user to confirm the value appears in 15Five.

Fix 2 — Add a mapping for Start Date

  1. In Okta, go to Provisioning > Profile Editor.
  2. Click Mappings > Okta User to 15Five.
  3. Locate the startDate row.
  4. Select the Okta user profile field that holds the start date value.
  5. Click Save Mappings.
  6. Trigger a sync for an affected user to confirm the value appears in 15Five.

Fix 3 — Correct the Location mapping formula

  1. In Okta, go to Provisioning > To App.
  2. Locate the Location attribute row.
  3. Set the mapped value to: String.join(", ", user.city, user.state, user.countryCode)
  4. Click Save.
  5. Confirm user.city, user.state, and user.countryCode contain values on the Okta user profile.
  6. Trigger a sync for an affected user to confirm the location appears in 15Five.

What Resolution Looks Like

After a successful sync, the user's profile in 15Five shows the expected start date value under their profile details. The Location field displays a comma-separated string in the format City, State, CountryCode. No blank or null values appear for these fields after provisioning.

If It Still Fails

Contact 15Five Support at support@15five.com. Provide the following:

  • The affected user's email address
  • A screenshot of the attribute configuration in the Profile Editor (namespace and variable name visible)
  • A screenshot of the Okta User to 15Five mapping for the failing field
  • The SCIM payload log from Okta (if accessible), showing the POST or PATCH request sent for the affected user

Not Covered Here

This article covers start date and location only. For hire date, termination date, or custom attribute sync failures, see the related articles below.

Related Articles

Was this article helpful?

Sorry to hear that. Tell us what was missing →