timhiebenthal

Yes, please! If it's already available anyway it would be a low-hanging fruit to make row-level-security even more powerful :)

Yeah, the issue still persists afterwards (Also noticed the comma right after opening the issue :D)

same issues, elementary-dbt: 0.16.0 elementary-python: 0.16.1 dbt core: 1.8.6 dbt-bigquery: 1.8.0 BigQuery as database Slack as messenger the `elementary_test_results` model has an empty field `result_rows` in case that helps. so...

thanks @ofek1weiss but to my understanding we did exactly that, right?  and yes, we use dbt 1.8  

We have a new implementation of Elementary so pointing it to a certain version upgrade is tough regarding question 1 and 2. we implemented the newest versions right away (dbt...

Update: I achieved the expected result with the following versions: ``` Elementary version 0.15.1. ``` dbt ``` Core: - installed: 1.8.6 - latest: 1.8.6 - Up to date! Plugins: -...

Seems to also work with dbt-package `0.16.1` How about you @christopherekfeldt ?

try the dbt package 0.16.1

Hey I stumbled across the same problem recently. One the one hand it's nice that jinja-variables are actually filled up with the real value, but in the case of doc-strings...

Ok fair, then let's ignore the package of model_usage which indeed uses the Information-Schema to check if a model is QUERIED. Probably you indeed need to exclude the dim/fact/reporting-layer, but...