1 | Build and run a SQL query (in Redash) to pull the information you need for the import:
Note: In the SQL, update team_type name that you would like to set a budget for
| select team_id as internalId, team_daily_rate as dailyRate, team_name, team_type, team_hierarchy_name_1, team_hierarchy_name_2, team_hierarchy_name_3, team_hierarchy_name_4, team_hierarchy_name_5 where team_type in ( 'Chapter', 'Capability' ) order by team_hierarchy_name_1, team_hierarchy_name_2, team_hierarchy_name_3, team_hierarchy_name_4, team_hierarchy_name_5 |
2 | Export a CSV file with the results |
|
3 | Build and run a SQL query (in Redash) to pull the information you need for the import:
Note: In the SQL, update team_type name that you would like to set a budget within
| select team_id as internalId, team_daily_rate as dailyRate, team_name, team_type, team_hierarchy_name_1, team_hierarchy_name_2, team_hierarchy_name_3, team_hierarchy_name_4, team_hierarchy_name_5 where team_type in ( 'Tribe', 'Crew' ,'Domain') order by team_hierarchy_name_1, team_hierarchy_name_2, team_hierarchy_name_3, team_hierarchy_name_4, team_hierarchy_name_5 |
4 | Export a CSV file with the results |
|
5 | In your supply CSV downloaded file, make sure you have the following 2 headings:
| |
6 | Open in your demand team ID CSV file For each demand team ID where you want to set a given budget against the relevant supply team, paste in the demand team ID into the supply CSV file with the intended budget in the following format:
CAUTION there is no way to set the budget to the demand team directly now as budgets were designed with the assumptions that supply teams would give demand teams their budget because they control the people | |
7 | If there isn’t a data source created for the import, create one. For some customers, we use the Teams CSV file upload (see icon on the right for reference). | |
8 | Upload the file The only two columns that need to be mapped are ‘InternalID’ and ‘budget’. |
General
Content
Integrations