Semantic model
The Semantic Model dropdown uses external data similar to the "Visual fields" dropdown. The data in this dropdown is fetched directly from a semantic model in Power BI. The advantage of this approach is that you don’t have to manually drag fields into the fields bucket.
To fetch data from a Semantic model, the user must have access to the workspace.
If the user is a workspace viewer, it need Build permissions in the semantic model that you are referencing for RLS (Row Level Security) to work. See https://learn.microsoft.com/en-us/power-bi/connect-data/service-datasets-manage-access-permissions
The first time you select the Semantic model, you must grant Aimplan permission to access your semantic model.
To use the Semantic Model dropdown, you must select a Workspace, Semantic Model, and a table within the model.
The users who will use the report must have access to the selected workspace. If a user doesn't have access to the workspace an error will occur.
Once a table is selected, all columns within that table will be displayed in the dropdowns for the Key and Text columns. After selecting the Key and Text columns, the dropdown will be populated with data from the table.
When using data from a Semantic model, no filters or slices are applied. This means the data is not filtered based on the current selection.
You can use dependencies to filter the options in the dropdown. The dependency value comes from another column in the data input table. When you open the Dependency Column dropdown, you will see all the columns available in the grid. By selecting a column from the dropdown, the visual will check the Power BI table and filter out all rows that match the selected column. However, for the visual to filter correctly, it must know which field to check in the table. Therefore, you must choose a field in the Lookup Field dropdown.
For example, in the image below, the Semantic Model dropdown will display a list of “Products.” Each product in the table is associated with a “ProductGroup.” In the grid, the “Product” is stored in the “Item” column, and the “ProductGroup” is stored in the “ItemGroup" column. This is how you should configure the dependency setup.