How to map Workday AD Template Division to Active Directory Company attribute?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2026 03:37 AM
Hi,
We have a Workday → ServiceNow → Active Directory provisioning process.
During provisioning, Workday sends an AD Template Division value to ServiceNow. We need ServiceNow to use this value to determine and populate the appropriate Company value in Active Directory.
We have a mapping in a spreadsheet where:
Column A = AD Template Division value received from Workday
Column B = corresponding Company value that should be populated in Active Directory
For example, if Workday sends a particular AD Template Division value, ServiceNow should identify the
corresponding value from Column B and populate it in the AD Company attribute.
Is this type of mapping possible in ServiceNow? If so, where we can fine this information in ServiceNow?
below is the example of col A and col B
| Workday Division Code | Active Directory Company Name |
| Alliance United CA | Auto |
| NSA | Auto |
| Corporate Services | Corporate Services |
| Home Service Companies | Life |
| Reliable | Life |
| Union National Life | Life |
| United | Life |
| Direct | Personal Insurance |
| Preferred | Personal Insurance |
| Services Group | Property and Casualty |
| UBI | Property and Casualty |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi, yes — this is a standard many-to-one lookup, and you should not hard-code it in the flow or keep it only in a spreadsheet.
Recommended setup:
1. Store the mapping as data in ServiceNow. Create a small mapping table (for example u_workday_division_company) with two fields: Workday Division Code (unique) and AD Company Name. Load your spreadsheet into it once. Your example is many-to-one — Alliance United CA and NSA both map to Auto — so Division is the key and Company can repeat. A Decision Table in Decision Builder works too, but a simple table is easier for HR/ops to maintain.
2. Look it up during provisioning. In your Flow Designer provisioning flow, before the Active Directory Create/Update User action, add a Look Up Record step on the mapping table where Division Code = the AD Template Division value received from Workday. Pass the returned AD Company Name into the Company input of the AD spoke action.
3. Handle the no-match case explicitly. If no mapping row is found, do not create/update the AD account with a blank or guessed Company — stop that branch, log the unmatched Division value, and raise a task/error for the team that owns the mapping. New Workday divisions are the usual cause of failures here.
4. Keep the values exactly as Workday sends them. Match on the code as received (watch leading/trailing spaces and case), and review the table when Workday adds or renames divisions.
Because the mapping lives in a table, you can add or change a Division -> Company row without editing and republishing the flow.