Sending us your data
Importing your team structure into DX involves sending a csv file to DX with your team information within. There are a few ways of accomplishing that.
A Workday RaaS Connection
API
Slack or Email to your CSM
Workday RaaS
This is configured in the product here: https://app.getdx.com/admin/workday_raas
This method sets up a direct connection between DX and one specific Workday report that then allows us to download and re-import your team structure at-will. It requires a bit of coordination up front, but once it's configured, then there's no further manual work from you.
The required fields for this option are spelled out here.
API
This method simply allows you to send us a CSV file via API. It must be a csv file and can be either of type user
or team
. Once the files are sent, they can be viewed here: https://app.getdx.com/admin/org_csv_uploads
Here is the API documentation:
POST https://api.getdx.com/org_csv_uploads.create
Parameters:
file (required) - CSV file (max 10MB)
upload_type (required) - Can be either `user` or `team`
cURL:
curl --location --request POST '/org_csv_uploads.create' \
--header 'Authorization: Bearer <your-token>' \
--form 'file=@"/examples.csv"' \
--form 'upload_type="user"'
We don't enforce the format of these files, but they can abide by the formats spelled out here, or feel free to reach out and we can provide some recommendations based on your source system data.
Data Structure
We want you to be able to provide the data to us in a format that is easiest for you to do so. This is different for everybody and so our requirements are flexible.
The most important things to be included in any team data are the email addresses for individual team members as well as team leaders/managers.
The data can be a simple reporting structure with contributor email and their manager's email, or as robust as the full team hierarchy with all levels.
You can find more detail on recommended data structures here.
Other Notes
It’s important that this report includes everyone in the organization, not just snapshot participants. You can add a column called exclude_from_snapshots
to your data to indicate the users will not participate in the snapshot.
If your internal team data system has a concept of unique ID's for teams, you can add those to the file in order to make future team updates straightforward - especially in the event of team name or manager changes.
We are also able to import the teams independently from the users. So if you'd first like to solidify the team structure and then later, assign users to their respective teams, that's a possibility as well.
Please reach out with any questions, and we'll be happy to advise.