Support

Excel export says the download is unavailable

A Fabric administrator needs to enable one tenant setting: Admin portal → Tenant settings → Power BI visuals → “Allow downloads from custom visuals”. Two things worth knowing: it is off by default in every Power BI tenant, and it is separate from your general Export and sharing settings — so a tenant that permits normal exports can still block this one. Pro Table names the exact switch on screen rather than failing silently. This is a Power BI platform gate, not a visual limitation.

Does my data leave my tenant?

No. All six visuals compute everything inside the Power BI session on your machine or in your browser. They make no external service calls of any kind. Nothing is transmitted to PBIStack or any third party — see the privacy policy.

Why don’t the statistics match another tool?

Usually because the other tool used a different method without saying so. There are several legitimate definitions of a quartile, and they disagree on small samples. Statistics Suite lets you pick — Tukey hinges, Excel’s QUARTILE.INC, or QUARTILE.EXC — and names the active method in the tooltip. Set it to match Excel and the numbers agree exactly; we verify that against QUARTILE.INC, QUARTILE.EXC, MEDIAN, AVERAGE, STDEV.S and CORREL before every release.

My control limits look wrong after a process change

They probably are — and that is what rebasing is for. Limits calculated across a step change describe a process that no longer exists, and they hide the very shift you care about. Freeze limits after a baseline of N points, let Control Charts Pro detect the step automatically, or supply a Phase field to control the split explicitly.

The Cohort Matrix warns about too many rows

The visual caps input at 300,000 rows and tells you when the cap is hit rather than silently truncating. Use month-grain date keys instead of timestamps, add a measure to the Value well (prevents dimension cross-joins), or pre-aggregate and use pre-computed mode. Details in the tutorial.

Someone is missing from my org chart

Org Chart Pro never drops a row silently, so start with the banners at the top of the visual: repeated IDs, blank IDs, reporting loops and self-references are named there. If the banner is quiet, the row never reached the visual — Power BI removes rows whose measures are all blank before any custom visual sees them. Keep one always-filled number (headcount or FTE) in the Value field and the row comes back. Details in the tutorial.

People appear at the top level who should not be roots

Their manager is outside the current view — filtered out by a slicer, or missing from the data. The visual keeps them on the chart at the top level and says so in a note, because deleting a whole branch when a manager falls outside a filter is how trust in a report dies. Widen the filter, or fix the manager ID in the source.

Photos do not show in the org chart

A certified visual cannot call external services, so photos come from your data: a URL your tenant can reach, or an image embedded as a data URI, which always works. People without a picture get coloured initials, so a missing photo never looks like a broken card.

Dates show a “hierarchy detected” message

Power BI's automatic date hierarchies deliver year/quarter levels as separate columns, which cannot be recombined into real dates. Use the plain date column (right-click the field → remove hierarchy), or a text key like 2024-09.

Why do the radar’s spokes show different scales?

Because their units are different. On a shared scale, a revenue spoke crushes a 1–5 rating into the centre — so Radar & Polar Pro lets each spoke use its own range, and says so: the ring labels switch to percentages and every tooltip names the actual value and the scale in use. If you want strict comparability, set Scale to “One scale for all spokes”.

Why is there a gap in my radar outline?

A blank is missing data, not zero. Drawing it at the centre would invent a reading, so the honest default leaves the outline open and a note counts the gaps. You can choose “Draw at the axis minimum” or “Hide the whole shape” in Data handling if your report needs it.

A lower-is-better target shows green

In v1 the radar treats targets as higher-is-better, so a cost metric that exceeds its target reads as “meets”. Direction-aware targets are the first v1.1 item; until then, consider inverting such measures (e.g. plot efficiency instead of cost).

Can I try before buying?

Every visual will have a free tier through AppSource at launch. Email us for early access.

Feature requests

Genuinely welcome — several shipped features started as user emails. Tell us the business problem, not just the feature; it usually gets solved better that way.