> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/working-with-inforiver/4.-adding-business-logic-and-formulae/insert-manual-input-rows/insert-manual-input-rows/insert-manual-input-rows-1/insert-rows-from-semantic-models.md).
# Insert rows from semantic models
{% hint style="danger" %}
This option is deprecated. The Inforiver Lookup visual is the preferred option to fetch data from semantic models.
{% endhint %}
You can also insert rows and their leaf categories from semantic models. The procedure is similar to [adding single and multi-select options from the semantic model](https://docs.inforiver.com/working-with-inforiver/4.-adding-business-logic-and-formulae/insert-manual-input-rows/insert-manual-input-rows/insert-manual-input-rows-1/pages/Z1VqW9RopnaOKKEZcFqT#id-2.-creating-a-lov-from-a-semantic-model).
### Step-by-step guide to importing data from semantic models
**STEP 1:** To pick and upload row categories from a semantic model, navigate to Insert > Manage Rows > Insert Row Settings > Create Row Configuration > Manage. Select **Options list from Semantic Model** from the 'Category' dropdown.
**STEP 2:** The **Add options from Semantic model** window opens. In the **Table Connection** tab, select the workspace, semantic model, and the table you need to connect to. Click **Next.**
Table Connection
**STEP 3:** Go to the **Options configuration** tab and choose the column from the connected table that will be used as the option label. In the example below, we have chosen the column 'Category' from the table 'Contoso-Product'. This column's members will be used to populate the 'Categories' row level.\
\
**STEP 4:** You can optionally specify a filter if hierarchical data is involved, and you want to maintain the same structure in your reports. In the **Columns** dropdown**,** select the field based on which you need to filter the options. In this case, it is the Contoso - Product.SubCategory which can be used to identify the Category. Select the matching field from the visual (SubCategory) in the **Visual Column** dropdown.
Then click **Add**.
Because of this filter, when you insert a row and add a sub-category first, you will be prompted with the category to which it belongs.
Options configuration
{% hint style="info" %}
Configuring filter options is optional. By adding it, we ensure that the dropdown list for each category displays only the relevant sub-categories and vice-versa. For example, if you choose "Cellphones" as the category, only the sub-categories under "Cellphones" will be displayed, not other categories.
Similarly, when you choose a sub-category, you can add it only under the relevant category.
{% endhint %}
**STEP** **5:** Follow the same steps from 1 to 4 for SubCategory dimension.
Options list from semantic model
Options Configuration
Configuration done
Once the configuration is completed as shown in the image above, you can follow the steps in sections 2.1/2.2 to insert the configured row categories into your visual.
You will see the data from the semantic model in the Category and Sub Category dropdowns.
Insert rows from semantic model
The rows are inserted as shown below:
Inserted rows
{% hint style="info" %}
The base data in our visual may be from one table, but the options in the dropdown may be from a different table; in such cases, you can specify a join. For more information on using joins and filters, please refer to [this section](https://docs.inforiver.com/working-with-inforiver/4.-adding-business-logic-and-formulae/insert-manual-input-rows/insert-manual-input-rows/insert-manual-input-rows-1/pages/Z1VqW9RopnaOKKEZcFqT#id-4.-using-joins-and-filters).
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.inforiver.com/working-with-inforiver/4.-adding-business-logic-and-formulae/insert-manual-input-rows/insert-manual-input-rows/insert-manual-input-rows-1/insert-rows-from-semantic-models.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
