Skip to main content
Omni imports most of a Snowflake semantic view definition. This page lists the parts that don’t import, and the parts that import in a fixed way. If you need one of these, reach out to Omni support.

​
Verified queries aren’t imported

Verified queries defined on a semantic view don’t import. The generated topic has no sample_queries.

​
Relationships always import as many_to_one

Snowflake doesn’t expose the cardinality of a relationship, so every relationship imports with relationship_type: many_to_one from the foreign-key table to the referenced table.

​
ASOF and RANGE relationships aren’t imported

ASOF and RANGE relationships aren’t imported. The topic imports without those joins. A view left with no relationship to the rest of the topic gets a validation warning.

​
Fields Omni can’t parse aren’t imported

A field whose SQL expression Omni can’t parse isn’t imported, along with any field that references it. The rest of the semantic view still imports as a topic. See Troubleshooting for more information.

​
Topics don’t follow dbt virtual schemas

Semantic view topics query the tables named in the semantic view’s definition, so switching your dbt environment doesn’t change what they read. Use included_schemas to import from your production schema only. Also include every schema that the semantic view’s tables use. See Which schemas Omni imports from for an example. Topics can’t follow dbt virtual schemas.

​
Next steps