My example also contains some other features. Finally, add this latest calculated field to filters and tick TRUE.Make sure it’s a string format, but no need to worry about the values since these will be updated through our parameter action. The drilldown works by filtering out branches whose IDs donot match the pattern of the last selected Path field. Instead I will focus on the steps to create the dynamic drilldown. I won’t go into the detail of every step I followed to buildmy org chart, but you can unpick the detail by downloading the Tableau Publicworkbook. You may also want to include other fields in this dataset such asemployee/manager names, teams, # of direct reports, whether they are a manager etc.You could also leverage Tableau’s relationships functionality to bring in thisinformation. In Alteryx,once I joined to create T, I used the following row-level formula to create T2:+(12*(-1)). The T2 field isa little more difficult as it depends on the level of the branch. As described in hisblog, the T field can be created with a simple lookup table for each branch(your 1 row per branch table will then become 49 rows/branch). These are the T and T2 fields from Jeffrey Shaffer’stemplate that constitute the individual coordinates of the curved lines. Once you have all the bulleted elements in your dataset, youcan create the full dataset of individual coordinates that will create thecurved lines of the chart. Note the same number of delimiters inevery row. The format of the path looks odd but it will be importantfor the functioning of the parameter.

Later on when we set up theparameter action to drill through the levels in Tableau, the fact that allparent nodes are stored in child nodes’ paths will ensure that earlier branchesdon’t disappear from the view. The bottom branch paths contain information about every nodethat has been passed through up until that point. Personally, I automated this aspect of the prep using Alteryx. As a side note, this is why it was actually more difficult to build a static org chart - because I had to find a way to ensure that nodes were evenly spread out in such a way as to group them into teams on a given level, but also as close to their parent as possible. Eg: for a parent node at position 5, level 2 with 3 ‘children‘ - their positions could be 4, 5 and 6 on level 3. This means you don't need to worry about nodes overlapping one another and you can simply attribute X positions based on the optimal spacing relative to the parent. By team I mean all nodes that share a parent (i.e. Because the chart will be dynamic, only 1 team can be opened at once. If you're dealing with a small dataset you can manually figure out the layout of the chart (the X and Y positions mentioned above). I also recommend giving each node a unique ID number – I use this tocreate the path field later on. Start and end level (this will later be used to determine the Y axiscoordinates).Start and end position (this will determine the X axis coordinates ofthe start and end of the branches).I called this field ‘Branch’ and thisis the same as Jeffrey Shaffer’s ‘Category’ field. A unique identifier for the branch (this could be a description of thebranch such as Manager A to Employee B).

In short, don’t see the rows as the points ofthe org chart, but as the lines that connect them.Īt the end of this step you should have a dataset whichcontains (at the very least): Further down the line, JeffreyShaffer’s Tableau logic draws the branch lines using the X/Y positions of thesebranches while the nodes are derived in table calculations that determine thestarts/ends of these branches. I suggest you first get to a point where you have a dataset where each row represents a branch of the chart. You can also watch how I built the chart in this YouTube video. This chart will also let you search for specific individuals and to highlight or filter by team. So I set out to build a view where you could toggle from a whole org perspective (though filterable by team) to an interactive drilldown that could build on what I saw in WorkDay and hopefully engage stakeholders. The chart would open when I didn’t want it to and it didn’t keep context from higher levels of the hierarchy. I started playing around with this chart type after a frustrating session trying to get my head around a client’s org structure in WorkDay. Ever wanted to build an org chart in Tableau or wondered if it was possible to make it interactive? Look no further! This blog will take you through the steps of building a dynamic org chart and point you to the templates you'll need to get started.īefore reading any further though, make sure you are using at least Tableau version 2019.2 – the drilldown functionality works off of parameter actions, first introduced in that version.Ī bit of background first.

Tableau public 2019.2 download