Auto Dashboards: Best Practices and Guidelines

The following topic is a practical guide to generate dashboards from screenshots and natural-language instructions, refine results, and prepare them for business use. See the topic for the following information:

  • Use Auto Dashboard to accelerate creation, not to guarantee an exact visual copy of a reference image.

  • Match the image’s analytical objects to attributes and metrics available in the selected Strategy dataset.

  • Use image generation for a first-pass, single-page, auto-layout dashboard and use natural-language instructions and manual editing to extend it.

  • Review calculations, filters, data sources, layout, and interactions before publishing.

Choose the Correct Creation Method

Auto Dashboard can create analytical content using an uploaded image or natural-language instructions. Choose an option based on the outcome you need. Image-based generation interprets a visual reference. It does not import the original dashboard’s business logic, interactivity, or exact design specification.

Image-based generation Natural-language instructions
Best for: recreating the broad analytical content and composition of a reference screenshot. Best for: specifying measures, dimensions, additional pages, and interactive elements.
Creates a single page using automatic layout in the image workflow. Can be used to request multiple pages and supported dashboard objects.
Requires matching or similar existing attributes and metrics; does not derive new metrics from the image. Can request derived metrics and supported navigation, selectors, panel stacks, and visualization filters.
Do not expect text boxes, navigation menus, or precise styling to be reconstructed from the image. Describe these elements explicitly; review and adjust the result as needed.

Prepare the Dataset

Before uploading a screenshot, identify the analytical objects it contains and confirm that the selected dataset exposes their Strategy equivalents. A visually similar label does not guarantee the same business definition.

  • Inventory the KPIs, chart measures, grouping attributes, time attributes, and filters visible in the reference.
  • Check metric names and definitions, aggregation, date logic, units, and supported levels of detail.
  • Prefer descriptive names that closely match the reference (for example, “Open Orders” and “Service Level %”).
  • Confirm that the required visualizations have a comparable out-of-the-box Strategy chart type.
  • When several datasets are present, verify which dataset the generated objects actually use.

Use Screenshots Strategically

Upload a clear, legible screenshot with a limited number of standard visualizations. The best results typically come from references whose metrics and attributes exist in the dataset and whose charts map to available Strategy visualizations.

Recommended Workflow

  • Start with one analytical page rather than a full application screen.
  • Focus on core KPIs, bar or line charts, and detail grids. Treat decorative elements as optional.
  • Generate the first draft from the image and inspect the objects created.
  • Correct mismatched attributes, metrics, chart types, and titles before refining styling.
  • Use natural-language requests or the dashboard editor for navigation, filters, formatting, and additional pages.

Screenshots do not encode interactions. A visible tab, search field, button, or alert may be only a visual cue. Describe the desired behavior separately instead of expecting it to be inferred from pixels.

Provide Precise Natural-language Instructions

Use specific names, placement, and behavior. Build in small increments so that each change can be reviewed.

Initial creation

“Create an operations overview page with KPI cards for Open Orders, Total Units, and Service Level %. Add a bar chart of orders by status and a detail grid by facility.”

Add a calculation

“Create a derived metric for Open Order Rate as Open Orders divided by Total Orders. Format it as a percentage and add it to the KPI row.”

Add interactions

“Add a selector for Facility and a navigation panel for the Overview, Performance, and Details pages.”

Refine a chart

“Change the orders-by-status visualization to a horizontal bar chart, sort descending, and use clear data labels.”

Add a page

“Create a second page focused on facility performance with an SLA comparison chart and a facility-level detail grid.”

Capabilities may depend on your Strategy version and environment. If a request is not completed, use the editor to finish the object and report reproducible failures through support.

Refine Formatting and Navigation

Use the first generated page as a starting point, refine chart titles, backgrounds, colors, labels, spacing, and number formatting.

  • Create navigation after the destination pages exist. Configure the available navigation object and its position in the editor.
  • Reuse a well-formatted page or visualization where appropriate instead of repeating every formatting step.
  • Use copy and paste formatting for similar visualization types. Some settings may not transfer between different chart types.
  • Consider supported themes for consistent appearance. Check how each chart type responds.
  • Review selectors and filter panels after copying content across pages, since chapter-level filters are not necessarily copied with individual visualizations.

Understand Practical Limits

Expectation Practical guidance
Exact visual reproduction Do not assume pixel-perfect fidelity. Automatic layout and available visualization types determine the first draft.
One screenshot → full multi-page application Image generation is page-oriented. Request additional pages and navigation separately.
Complex KPI cards with embedded trends or annotations Build the core metric first; use supported objects or manual formatting for the remaining presentation.
Text, decorative boxes, search, and navigation in a screenshot Do not rely on image upload to create them; specify behavior through natural language or add manually.
Calculated measures inferred from screenshot labels Create and validate calculations explicitly rather than relying on image interpretation.

Troubleshoot Systematically

Symptom Recommended check
A KPI is missing or wrong Check matching metric availability, definitions, filters, date scope, and dataset selection.
The chart differs from the screenshot Check visualization support and attribute/metric mapping; request a supported chart type.
Navigation or selectors are absent Create destination pages, then request or configure navigation and selectors explicitly.
Styling differs Use manual formatting, formatting reuse, and available themes.
A request times out Retry a smaller analytical request; capture exact steps and error details for support.
Copied objects lose settings Check chapter-level filters and object-specific formatting; escalate reproducible unexpected loss.

Validate Before Sharing

  • Every KPI matches a trusted reference for the same date range and filter context.
  • Metric definitions, aggregation, formatting, and units are correct.
  • Charts use the intended attributes, sorting, and supported granularity.
  • All required pages, selectors, filters, and navigation work as intended.
  • The result is legible and usable on the intended screen size.
  • Unsupported or incomplete elements have been finished manually or explicitly documented.

Recommended End-to-end Workflow

  1. Prepare data.

  2. Choose screenshot or natural-language creation.

  3. Generate first draft.

  4. Verify metrics and charts.

  5. Add pages and interactions.

  6. Refine formatting.

  7. Validate and publish.

Additional Information

Auto Dashboard: Dashboard Page Design

Described features and limitations are version-specific and subject to change. Consult the documentation for your deployed version.