# Lookup visuals for dropdowns The Inforiver **Lookup visual** has been designed to help you seamlessly integrate data from different semantic models into your reports and ensure that the data is up-to-date and accurate. {% hint style="info" %} This feature is available only for Writeback Matrix. {% endhint %} ### 1. Top 3 benefits of using the Inforiver Lookup visual * You can fetch data from your source tables in real-time, provided you have an up-to-date semantic model or the lookup table is in direct query/lake mode. * Row-level security is implicitly handled as the helper visual displays the list of values based on the data Power BI transmits for a particular user. * The lookup visual is lightweight and requires virtually no maintenance, like data refreshes. ### 2. Importing and configuring the Lookup visual The Inforiver Lookup visual works in tandem with the Matrix visuals. It can be downloaded from our [customer portal](https://inforiver.com/login/) for free and then [imported](https://docs.inforiver.com/introduction-to-inforiver/get-started/installing-inforiver-for-yourself) into Power BI.

To configure the visual, simply drag the dimension with dropdown options from your **semantic model** into the **Dimension** field. You can add multiple lookup visuals for a single Inforiver Matrix visual.

Adding lookup visuals and assigning dimensions

### 3. Sourcing single-select and multi-select options from the Lookup visual The lookup visual is a more efficient solution that overcomes the drawbacks of connecting directly to the semantic model from Inforiver – the data is refreshed automatically when the Power BI semantic model is refreshed, and RLS settings are honored. ### 4. Creating a dropdown with Lookup visuals **STEP 1:** Select the **Lookup Visual** option and specify the lookup visual name When you choose the Lookup Visual option, you must specify the visual name in the configuration. In this case, we are populating dropdown options for the manager’s name – so we’ve selected the corresponding visual name.

**STEP 2:** Assign the dimension field to source dropdown options Next, select the **Column Label** field – the options in the dropdown will be sourced from this field. If you have a primary key or ID field associated with the label field, you can assign the ID field to the **Column ID**. If the column labels are updated, the ID field mapping ensures that the updated value will be reflected in your reports. Note: If your lookup table has no ID field, use the same label field (in this example, Manager Name) as Column ID.

**STEP 3:** Click **Add** to apply the configuration and **create** the dropdown. ### 5. Ensuring data integrity for dropdown options Let’s take a closer look at assigning a manager from the dropdown. Suppose a manager has jurisdiction over the 'South' and 'East' regions only – but he is incorrectly assigned as an approver for a product category in the 'Central' region. A manual error such as this one in selecting options could result in ambiguity, delays, and possible financial losses. When you deal with huge data volumes, such operational errors are inevitable. With Inforiver, you can enforce data integrity by specifying filters while configuring dropdowns. Please be aware that to use **filters**, the dimension (in this case, Region) needs to be added to the Inforiver and Lookup visuals.

Let’s look at the dropdown in action. With filters applied, notice how the options change dynamically based on the region.

### **6. Automatic cross-filtering** The lookup visual has the added capability to cross-filter data. The sample report shown below sources product data from a lookup visual. Notice how the product names change dynamically based on the product sub-category. {% hint style="info" %} * Power BI **Edit interactions** toggle needs to be enabled for cross-filtering to work correctly. {% endhint %}

Disable the **cross-filter** option to pull all the data from the lookup visual, irrespective of the row dimension category in the matrix visual.

--- # 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.inforiver.com/working-with-inforiver/4.-adding-business-logic-and-formulae/insert-manual-input-columns/dropdown/lookup-visuals-for-dropdowns.md?ask= ``` 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.