Non-Data Visuals
What It Detects
Section titled “What It Detects”This flag identifies visuals on report pages that are not bound to any data field — they do not query the dataset and exist purely for layout or decoration purposes. These include:
- Images and logos
- Shapes (rectangles, lines, dividers)
- Text boxes with static text
- Blank/spacer visuals
- Decorative HTML content visuals
Why It Matters
Section titled “Why It Matters”- Visual clutter — Non-data visuals contribute to the total visual count on a page, which impacts rendering performance even if they don’t generate DAX queries.
- Maintenance overhead — Decorative elements often need manual updates (e.g., updating a company logo, changing a header text) and can break page layout when the report is resized.
- Accessibility — Images without alt-text and decorative shapes can confuse screen readers and reduce accessibility compliance.
- Report file size — Embedded images increase the .pbix file size, making it slower to publish and download.
Trigger Conditions
Section titled “Trigger Conditions”A visual is flagged as non-data when:
- The visual has no data field bindings (no columns or measures in any data role: values, axis, legend, filters).
- The visual type is one of:
image,shape,textbox,basicShape,html, or any custom visual with zero data roles populated.
A report page is included in the output when it has 5 or more non-data visuals.
Threshold: ≥ 5 non-data visuals per page (default).
Output
Section titled “Output”| Field | Description |
|---|---|
reportName | Report name |
pageName | Page name |
nonDataVisualCount | Number of non-data visuals on the page |
totalVisualCount | Total visuals on the page (for context) |
nonDataTypes | List of non-data visual types found (e.g., “image, shape, textbox”) |
workspaceName | Workspace name |
Notes and Edge Cases
Section titled “Notes and Edge Cases”- Branding templates — Many organizations use a standard report template with header images, logos, and footer shapes. These are expected and may not need remediation, but should be tracked.
- Slicers vs. text boxes — A slicer with no field bound is flagged as non-data. Ensure slicers are properly connected to a column.
- Custom visuals — Some custom visuals may not report their data bindings through the standard API. These may be falsely flagged.
Related Flags
Section titled “Related Flags”- Excessive Visuals — High total visual count on a page, including non-data visuals.