This message was deleted.

Yea, we ran into this problem too...when dbt rebuilt views Secoda was losing visibility at the schema level. So you are correct that the reference commands need to be at the schema level.

@agreeable-fish-22746 Not sure if this is helpful for your support ticket, but I had problems on the same step. (FYI @elegant-house-93198)

Thanks @dry-thailand-84510!

Thanks @dry-thailand-84510. I'm essentially trying to setup Secoda with a catch-all command as I know a few other data discovery tools use the

snowflake

database to generate all documentation and lineage. Which is a lot simpler to setup

GRANT IMPORTED PRIVILEGES ON DATABASE SNOWFLAKE TO ROLE ROLE;