> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omni.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Querying Snowflake semantic view topics

> Where imported Snowflake semantic view topics appear in Omni and how to query them in workbooks.

After a [schema refresh](/modeling/develop/schema-refreshes) imports your semantic views, each one is a topic you can query like any other. This page covers where the topics appear and what to expect when querying them.

## Where the topics appear

Imported topics carry a **Snowflake mark** in the topic picker, field browser, and model IDE; hover it to see the fully qualified semantic view name. In the IDE file browser they sit in a **Snowflake Semantic Views** folder. Set a [`group_label`](/modeling/topics/parameters/group-label) to move one into a group of your own.

## Querying a semantic view topic

In a workbook, pick the topic and select fields as in any other topic. Filtered measures, level-of-detail calculations, dynamic top N, column totals, period-over-period comparisons, pivots, and [composite topics](/modeling/composite-topics) all work.

Metrics use [symmetric aggregates](/analyze-explore/sql/symmetric-aggregates) keyed on the `PRIMARY KEY` of the logical table the metric reads from, so a metric queried across a one-to-many join counts each row once.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Query messages on a semantic view topic">
    | Message                                                                                                                                                                                                              | What to do                                                                                              |
    | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
    | `No single join path connects all of "<view>", "<view>" in topic "<topic>". ...` — the selected fields sit on views the relationships don't connect in one direction, such as two fact tables that share a dimension | Add a field from the table that holds the foreign keys, or run separate queries.                        |
    | `"<field>" uses a window function, which Omni doesn't support on semantic view topics yet. ...` — also appears as `uses an aggregate in a dimension` and `nests one aggregate inside another`                        | Remove the field. A metric that references another metric, such as `${orders.count} + 1`, is supported. |
    | `Add a field from the topic to the query before saving this calculation to the workbook`                                                                                                                             | Add a field from the topic, then save the calculation.                                                  |
  </Accordion>

  <Accordion title="A metric is too high when combined with fields from another table">
    [Symmetric aggregates](/analyze-explore/sql/symmetric-aggregates) key on the logical table's `PRIMARY KEY`. Check that the logical table in the semantic view declares one, then run a [schema refresh](/modeling/develop/schema-refreshes).
  </Accordion>
</AccordionGroup>

## Next steps

* Learn [what Omni creates for each semantic view](/connect-data/snowflake-semantic-views/sync/trigger-sync)
* Look up [what each part of a definition becomes in Omni](/connect-data/snowflake-semantic-views/sync/metadata-reference)
* [Push a topic you built in Omni to Snowflake](/connect-data/snowflake-semantic-views/push-to-snowflake)