Skip to content

Bind Reports to Semantic Models

When you restore a report, choose which semantic model it reads: the one it used before, one restored from the same archive, or another model in the tenant.

How binding works

A Power BI report always points at one semantic model. On the restore wizard's Place step, each report row shows its binding in the Bind to card of the details panel, for example -> Sales (restored too) or -> Sales (existing).

MetaMiner binds automatically when it can:

Situation Automatic binding
The report's model is restored with it The report binds to the restored model.
The model is overwritten in place Same model, same id: the report stays connected.
The model is already in the target workspace The report binds to that model.
The model is restored as a copy (Keep both) MetaMiner asks whether the reports using it should point at the new copy or stay on the original.
The model is neither restored nor in the target The row shows Needs a model and blocks the run until you choose one.

A paginated report names its model inside the .rdl file, and Power BI does not expose that link, so a restore cannot point a paginated report at a different model.

Before you begin

  • You are on the Place step of the restore wizard (see Restore Content).
  • To choose a model from the tenant, the environment is loaded in the MMC Power BI Explorer. The tenant list is read from it.

Steps

  1. On Place, select the report row.

  2. In the Bind to card, click Change....

    The Semantic model dialog asks Which semantic model should "" use?

  3. Choose one option.

    Option When to use it
    Automatic: ... Follow whatever happens to the model the report was captured with. The label says what that is.
    Do not rebind (keep original model) Keep the report on the exact model it used when the backup was taken. Available only when that model can be seen to exist.
    A semantic model from this archive Point the report at another model being restored from this archive. Each entry says what the restore does to it: new, overwritten or a new copy.
    A semantic model in the tenant Point the report at any model in the environment. Type in Filter by model or workspace to search.

  4. Click Use this model.

    For a tenant model, MetaMiner first checks the model still exists (Checking that model is still there...), because the list comes from the last collection. If it was deleted since, the dialog says so; choose another.

  5. Check that the row's Bind to card and the grid now show the model, and that the row is no longer red.

Image of the Semantic model dialog with A semantic model in the tenant selected, a filter typed and one model highlighted

../images/backup-restore/bind-dialog.png

Image of the Reports using this model prompt asking whether two reports should point at the new copy of a semantic model

../images/backup-restore/bind-copy-prompt.png

Verify

On Review, select the report on the right-hand panel. Its detail line reads Semantic model: ... with the model you chose. After the run, open the report in Power BI and confirm it shows data (after the model's credentials are set and it is refreshed).

Troubleshooting

A semantic model in the tenant shows no models

The dialog says This environment is not loaded in the Power BI Explorer, so there are no models to list. Open the Power BI Explorer, load the environment, and open the dialog again.

Its original model was not found

The model the report used is gone from that workspace, or MetaMiner could not check it. Choose another model, or Re-check on the Place step.

The report opens but shows no data

A restored model has no credentials and, unless restored with .pbix data, no data. Set the data source credentials in Power BI and refresh the model.

Next steps