Manage native dashboard definitions

Use native dashboards when people need visual reporting built inside IFBI. An application integration usually works with an approved dashboard design, its dataset bindings and its audience rather than generating a new visual layout for every request.

Understand the two configuration layers

Dashboard Save manages the DashboardModel, including its name, description, dataset relationships and groups. Native visual design is carried in the dashboard definition. Saving metadata is not a general API for constructing every chart or designer interaction.

When listing dashboards, use IsIntellifrontDashboard to distinguish native content from integrated platform content. Retain the IFBI dashboard ID in your application mapping. Other identifiers, including DashboardNativeId and external Power BI identifiers, serve different purposes.

Reuse an approved design

1. Build and verify the visual design in IFBI with representative data.
2. Use Dashboard Export to retrieve the native definition. Its wrapped Data contains the XML definition string.
3. Prepare the intended target dashboard and map compatible dataset and connection references.
4. Use Dashboard Import with the documented target ID and multipart file upload.
5. Open the target dashboard as an intended reader and check its data, filters, parameters and access.

Definition reuse is a deployment workflow. Review source-to-target identifiers and dependencies rather than assuming all IDs remain valid after copying content between installations.

Keep definition export separate from report output

Use Dashboard Export to retrieve the XML definition for reuse or deployment. For rendered output, use the export options available in the IFBI dashboard viewer.

Similarly, a dashboard cache timestamp is operational evidence about the cache, not proof that all source data is current. See refresh history and freshness.

Choose the next integration step

Use canvases to combine dashboards and KPIs for a reporting audience. Use sharing and embedding for interactive viewing inside another application. Plan the viewer experience alongside the API calls that manage its content.