Versions Compared

Old Version 1

changes.mady.by.user Space Sync for Confluence

Saved on

compared with

New Version 2

changes.mady.by.user Space Sync for Confluence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
1

Build and run a SQL query (in Redash) to pull the information you need for the import:

  • Supply team name

  • Supply team ID

Note: In the SQL, update team_type name that you would like to set a budget for

  • eg: if you want to set supply budgets for Chapter Area only then just enter in ‘Chapter Area’ in the team type

Code Block
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:

  • Demand team name

  • Demand team ID

Note: In the SQL, update team_type name that you would like to set a budget within

  • eg: if you want to set supply budgets at the Domain level, then just enter in ‘Domain’ in the team type

Code Block
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:

  • Internal Team ID: this should be the heading for the list of supply team IDs

  • Budget

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:

  • demandTeamId:budget value

  • eg: W123XI:30000

Note

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

View file
nameapollo6 _budgets.csv

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’.

Related information

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@9e4
maxCheckboxfalse
sortmodified
showSpacefalse
reversetrue
typepage
cqllabel in ( "system-admin" , "workforce-planning" , "data-import" , "rates" , "financials" , "budgets" , "planner" , "forecast" ) and type = "page" and space = "OS"
labelsteam team-details types