Tutorial

Org Chart Pro in fifteen minutes

From a flat employee table to a finished organization chart: the two fields it needs, the optional ones worth adding, how it handles imperfect HR data, and every setting explained. Follow along with the sample dataset (29 people, one fictional company, with an open position, a dotted line and a job share already in it).

1. Quick start

  1. Add the visual to a report page.
    Once it is on AppSource: Visualizations → Get more visuals → search “Org Chart Pro”. Until then, import the .pbiviz file you received.
  2. Drop EmployeeID into Employee ID and ManagerID into Manager ID.
    That is the whole hierarchy. The person whose manager is blank becomes the top. Any unique key works — employee number, work email. If your table has only names, put the name in Employee ID and the manager's name in Manager ID; it works, but two people with the same name will merge.
  3. Add Name and JobTitle.
    The two lines on every card. Add Department to Group (colour by) and every card takes its department's colour, with a key above the chart.
  4. Look at the banners before you look at the chart.
    If the extract has a problem — someone reporting to themselves, a loop, a repeated ID, a row with no ID — the visual says so in plain words at the top, and keeps everyone on the chart. Nothing is dropped without telling you.
A full organization chart with photo cards coloured by department, a colour legend and open positions inside the reporting chain.
Four fields in, and the whole company is on screen with every card clear of its neighbours.

2. The fields

Field wellWhat goes inNotes
Employee IDThe unique key per person. Required (or key on Name — see above). Blank IDs are reported in the banner, not drawn.
Manager IDWho they report to, in the same terms as Employee ID. Required. Blank = a root. A manager who is filtered out of the view leaves the person at the top level with a note — not deleted.
NameThe main line of the card.Falls back to the ID if empty.
Job titleThe second line.Optional.
Group (colour by)Department, location, band — anything categorical. Colours the card accent; adds the colour key. Each group's colour can be overridden in Card design.
Photo URLAn image URL or a data URI. People without one get coloured initials. URLs must be reachable from your tenant; embedded data URIs always work.
ValueA number per person: FTE, headcount. Rolled up through the tree. Also the field that keeps rows alive — see the data note in section 8.
Cost / budgetSalary, budget, headcount cost. Summed down every branch, so a manager's card can show what their organisation costs.
Open position flagAny true / 1 / “Yes”. Marks an unfilled role. Open headcount rolls up and shows on every manager above it.
Start dateHire date. Tenure is worked out at render time. Use the plain date, not a date hierarchy.
Dotted-line managerA second reporting line. Drawn dashed. Never changes the tree or the numbers.
Badges (flags & KPIs)Several allowed. Each becomes a labelled pill on the card — Remote, Contractor, a rating.
Card detailsExtra lines on the card.Location, cost centre.
TooltipsExtra fields on hover.Anything you don't want on the card face.

3. Open positions and cost

Add IsVacant to Open position flag and AnnualCost to Cost / budget. Unfilled roles get a tag (or a dashed outline, or a tinted card — Format → Open positions → How) and a “1 open” pill appears on every manager above them, so a collapsed branch still shows what is open underneath. Switch on Span of control → Cost rollup and each manager's card carries the cost of their whole organisation. No DAX needed: the rollups are computed by the visual from the rows in view, and change with your slicers.

An org chart filtered by a department slicer with an open position card and open-headcount pills rolling up to the top.
Open headcount inside the chain, rolled up to every manager above it.

4. Matrix reporting and tenure

Put the second manager's ID in Dotted-line manager and the relationship is drawn as a dashed curve between the two cards — visibly different from the hierarchy, and never counted in any rollup. Put the hire date in Start date and tenure appears as a pill at the right of each card's header (11.7 yrs), or after the name if you prefer; Format → Tenure chooses the format, highlights new joiners under N months or long service over N years, and Sort can order siblings by it.

Dashed dotted-line reporting curves between cards, with tenure after every name and long-serving employees highlighted.
Dashed means dotted-line. The hierarchy and the numbers stay exactly as they were.

5. Card designs and colours

Format → Card design → Design offers six layouts: Header bar (name in a colour band — the default), Classic (photo left), Stripe (a thin colour bar on the left edge), Portrait (photo above, centred), Overlap (round photo on the card edge) and Compact (text only). Every design is a template, not a palette: canvas, card background, accent, border, corner radius and text colours are all yours. With Colour the accent by Group on, choose a group in Group to colour and pick its colour below; All groups sets one colour for every group in view, and the picker's Reset to default returns a group to its automatic colour.

Photos decides who gets one: everyone, managers only, or just the top levels — so a 5,000-person chart shows photos where they carry meaning and stays quick. Shape and size apply to every design that shows a photo.

Three org chart visuals side by side using different card designs and canvas colours.
Same data, three looks — the canvas colour is yours too, so the chart matches the report rather than the other way round.

6. Getting around a big chart

7. When the data is imperfect

HR extracts have problems, and an org chart that hides them is worse than none. Format → Data issues controls what happens:

SettingWhat it doesWhen to change it
Problem recordsShow everyone (default), hide people with problems, or show only them. “Show only” is a handy audit view to send back to HR.
Repeated Employee IDsReport the repeat and keep the first row, or merge the rows into one node (a job share). Merge when two people genuinely hold one position — names are joined, numbers summed.
Report data issuesThe banner naming loops, self-references, repeated and missing IDs. The ✕ on the banner switches this off for the report; switch it back on here.
Note people outside the viewThe note for people whose manager is filtered out. Turn off on pages where a department slicer makes this expected.
Mark affected cardsDashed amber border on the people involved. Leave on: it is how a reader finds them.
A banner naming three people in a reporting loop, shown at the top level with amber dashed borders, while the healthy hierarchy renders below.
A reporting loop, named in the banner and marked on the cards — and everyone is still on the chart.

8. Good to know

Something not covered here?

Ask — the answer usually ends up back in this tutorial.