# Dynamic models

Dynamic models, or Dynamic Dataset Binding, is a feature exclusive to Power Embedded and not available in the Power BI service, designed for scenarios in which a single report is accessed by different clients, each using a different semantic model, and therefore viewing different data.

It would be possible to have this same behavior by creating several reports to meet this need to view different data depending on the user who is viewing it, but if you need to adjust measures or even improve a visual, you would have to change all the reports, which could cause inconsistencies in data and calculations between reports.

Using dynamic templates, when you update a single report, everyone will see the changes in the same way, since it will only be a single report and N dynamically associated templates.

The biggest advantage of this functionality over row-level security (RLS) is in performance and security itself.

This is due to the fact that when you apply a lot of RLS rules to a semantic model, the model ends up being very large, as it contains data from several customers, for example, and this can cause a significant increase in the consumption of processing capacity, as each rule creates a separate subset of data internally.

A dynamic model will query a specific model depending on the user viewing the report, resulting in smaller, independent and isolated models, which can not only improve performance, but also strengthen security, even in cases of errors in the measures that control the RLS.

### Example of dynamic models

<div align="left"><figure><img src="/files/1mzCT7AKUlxBwlgJpprY" alt=""><figcaption></figcaption></figure></div>

Dynamic models allow different clients (Client A, Client B, Client C) to access the same report by applying filters at the model level. For example, if a user is associated with Model A, the system will dynamically connect the report to Model A without the need to filter the data manually.

**Usage Example**

When adding a model by clicking the **"Add Model"** button, you will have access to all imported datasets.

<figure><img src="/files/yEOzw8nWWearxKszJHlq" alt=""><figcaption></figcaption></figure>

You can select the desired dataset and assign users to that model.

<figure><img src="/files/z4DdTGP4c9R06CBhw83j" alt=""><figcaption></figcaption></figure>

From that moment on, when a user accesses the report, the semantic model will automatically change according to the assigned rule.

For example: When the user **"<cliente1@hotmail.com>"** accesses the portal, they will be identified as part of the **"Demo 01"** dataset and will only see information relevant to their profile.

It is possible to include multiple users and/or groups in a single dataset and associate multiple datasets with the report as needed, keeping in mind that the data structure (table names, columns, measures, and relationships) must be identical across dynamic datasets.

To assign a user to a dataset, simply click **"Actions" > "Manage"** and choose which users or groups will be part of it.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.powerembedded.com/administration-portal/reports/dynamic-models.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
