ProSankey Support

In Path mode, you need at least two fields in Levels and one numeric field in Value. In Graph mode, Source Node, Target Node, and Value are all required. Check that your Value column is numeric and contains non-zero values in the current filter context.

Path mode on the Free plan supports up to 3 levels. Levels 4 and beyond require a ProSankey Pro subscription. An upgrade prompt will appear in the visual when additional levels are bound but the license does not cover them.

ProSankey uses d3-sankey for layout. Very dense graphs (many small flows between the same set of nodes) can produce tight layouts. Try increasing the visual size, enabling the Top-N bucketing setting to reduce node count, or using performance sampling to limit nodes and edges to a manageable set.

No — that is a cycle arc. ProSankey's loop detector found a circular flow in your data (A → B → C → A) and is rendering it as a back-arc rather than crashing the layout. You can style or hide these arcs in Format panel → Cycles. Cycle arcs require a Pro license.

Check that each active Color Rule slot has a non-empty Rule Value that exactly matches the node label in your data. Matching is case-sensitive by default. Enable Case-insensitive matching in Format panel → Data if your data has inconsistent casing. Unused rule slots should be left with an empty Rule Value.

Flow labels require a ProSankey Pro license. If the setting is visible in the format panel but labels do not render, verify that your subscription is active in Power BI Service and that the license check has resolved (try reloading the report). Flow labels may also be hidden when the link band is too narrow — increase Min width in Format panel → Flow Labels.

Path tracing is a Pro feature. On the Free plan, click interactions trigger cross-filtering via selectionManager but do not activate path highlighting. Upgrade to Pro, or click away from all nodes and links to reset to the default full-opacity view if you see residual dimming.

Bucketing requires a Pro license. If licensed, ensure bucketing is enabled in Format panel → Bucketing and that the threshold percentage is lower than your smallest node's share of the grand total. If every node exceeds the threshold, no "Other" bucket is created.

Cross-filtering requires the visual to have at least one data role bound that Power BI can use to build a selection ID. Ensure your Source Node or Target Node fields (Graph mode) or Level columns (Path mode) reference columns from the same data model table as the target visual. Also check that Cross-filter type is set correctly in the report settings.

ProSankey includes a performance cache that skips redundant parse and layout passes. Enable it in Format panel → Performance → Enable cache. You can also reduce node count with Format panel → Performance → Max nodes and reduce edge count with Max edges. Viewport culling (also in Performance) skips off-screen elements automatically.