Notices and diagnostics
What each notice means, how to read the Diagnostics panel, and answers to common questions.
When Flow Globe sets data aside, it says so. A notice appears at the top left of the visual; click the panel to read it in full, with the rows concerned and what to do.
Notices
| Notice | Meaning and remedy |
|---|---|
| The welcome page: Fill these fields, in this order | Origin or Destination is missing. The page lists the three fields, marks those already added, and names what is still to add. Its Manual link opens this manual in your browser. |
| Add a Value measure to size the flows. | Each distinct combination of the fields counts as one until a Value is added. |
| N unrecognised places | These names were not found. Use a country, city, port or ISO code, or coordinates. See Place names. |
| N shared place names | Several real places share these names; one was kept. Add the country or the coordinates to pick another. |
| N places read as a country | A three-letter code in capitals is read as a country code (FRA is France). If it is an airport or port code, write the place name instead, or add the coordinates. |
| N places outside the given country or region | The country or region given - in the country column or after a comma - does not contain the place found. Correct it, or give coordinates. |
| Render limit reached | More flows than the render limit. The largest are drawn. Raise the limit in the Format pane, or filter the report. |
| Row cap reached | The visual stopped at 200,000 rows while Power BI still had more to send; some flows may be missing. Filter the report, or reduce the number of rows upstream (a report filter, or a wider aggregation level). |
| N rows have a Value that is not a number | Counted as 0. Usually a division by zero in the measure. |
| N rows have no origin or no destination | Left out. An end that is empty, or holds a spreadsheet error such as #N/A, counts as missing. Fill in both ends, or give their coordinates. |
| N rows with unusable coordinates | Not numbers, out of range, only half of the pair, or (0, 0). These ends are placed by name instead. Use decimal degrees within ±90 / ±180, and leave missing cells empty. |
| “Origin latitude” has no matching longitude | Only one coordinate field of a pair is in the wells: it is ignored, and places are located by name. Add the other field, or remove this one. |
| N routes have an objective on only part of their rows | In the Variance to objective view: treated as having no objective. Give an objective to every row of those routes, or to none. |
| Every row goes from a place to itself | Origin and Destination probably hold the same field. Check the wells. |
| At the “Countries” level, every flow stays inside a single place | All flows are internal at this level. Choose a finer level in Group by, or switch Display mode to Auto. |
| No flow matches the current filters. | Minimum value is above every flow. Lower it. |
| The field of the saved view is no longer available | The report was saved on a view whose field has been removed: Value is shown instead. Re-select a view, or restore the field in the model. |
| “Measure”: the type … does not match what the column contains. | The Measure type set in the Format pane does not fit the data. The visual applies it anyway; check the setting. |
| Add an Objective measure to enable Variance. | The Variance to objective view needs the Objective well. Add a measure, or ignore the view. |
| Add a Previous value field to use this view. | The What changed view needs the Previous value well. |
| N filtered out | Flows removed by Routes shown, Minimum value or Cover % of volume. |
| Colour choice ignored | A colour you set is too close to another and would flatten the ramp: it is not applied. Pick a more distinct shade. |
| No corridor to bundle | Bundling is on but no group of flows shares an endpoint and a direction (within the same 60° cone), so nothing can be bundled. |
| Colour thresholds ignored | The thresholds of a measure view must increase, and be written without a thousands separator. |
| N bundled corridors - paths are schematic | Shared legs are simplified for readability. Endpoints, totals and filters are exact. Select a flow to see its own path. |
| Bundling applies to the Value view only | Bundling is on, but the current view uses colour for something else. Switch to Value, or turn bundling off. |
| Too many flows to animate them all | The animation budget is exhausted: the smallest flows are still drawn, but without movement or direction mark. |
The Diagnostics panel
Open Options and choose Diagnostics. The panel shows the version of the visual and counts what happened to your data, line by line:
| Line | What it counts |
|---|---|
| Input rows | Rows received from Power BI; below it, rows merged into a single flow, rows whose two ends fall in one place at the current level, and rows going from a place to itself. |
| Valid routes / Rendered routes | Flows found, and flows drawn. |
| Hidden (render limit) / Filtered | Flows left out by the render limit, and by your filters. |
| Share of volume shown | The part of the total the map is showing. |
| Unresolved places | Names not found, listed. |
| Outside the given country or region | Places that contradict their country column. |
| Rows with no origin or no destination | Rows left out. |
| Cross-highlight · Selection gesture | What the report sent to the visual, and the last selection the visual sent back, with the host's response time. |
| Licence phase | Whether the licence check has answered, and whether the report is being read or edited. |
| Unusable coordinates · Aggregated coords | Rows whose coordinates were refused, and places whose coordinates look like placeholders. |
| Reciprocal flows · Bundling · Unique categories | How many of each; the bundling line appears when bundling is on. |
| Notices at the bottom | At the bottom, when they apply: render limit reached, high unresolved rate, more than 20 distinct categories. |
When you write to support, the version and a screenshot of this panel are the most useful things you can send.
Common questions
- A flow I expect is not on the map.
- Check, in this order: a notice about unrecognised places; Routes shown, Minimum value and Cover % of volume in Options; the render limit; and the level of detail - two cities of the same country make no arc at country level.
- The numbers are larger than in my table.
- The visual adds up the rows of a flow - across categories, and across the cities of a country at country level - so a stock or a rate gets summed. Keep an additive measure in Value, and put a rate in Extra measures with Measure type set to Rate or average. See Your data.
- A view is greyed in the view menu.
- Its field is missing: the menu writes which one under its name. It may also be a Premium view your licence does not include: choosing it, Power BI shows its own banner - Not included in your plan.
- The map reframes when I click.
- Turn on Lock view in Options, or turn off Fit on selection in the Format pane card Camera.
- A place is on the wrong continent.
- Its name is shared by several places. Add the country column, or write
City, Country. - Can I use it in Report Server, Publish to Web or Embedded?
- Write to us before you deploy: these environments behave differently, and we would rather tell you what to expect. See the support page.