hey all! is there a known issue with elementary writing “None” in the

job_run_url

field for the

dbt_invocations

table? • we recently upgraded our dbt Cloud from 1.4 -> 1.6. • we’re on Elementary version 0.8.3. do we need to upgrade to the latest Elementary to resolve this issue?

Hey @Charlie Hahn 👋🏼 Did it work as expected before?

hi @Noy Arie! thanks for reaching out and thinking of you all on the Elementary team… i believe it did work before. my colleague would click on this URL from the Elementary report, but now it’s showing “None”

Thank you @Charlie Hahn 🫶🏼 Can you please check some older records in this table? The account id is the

None

value in the URL. The URL is generated using the dbt var

account_id

or using the dbtCloud env var

ACCOUNT_ID

. I want to make sure that it worked so I could better understand what could go wrong 🙏🏼

thank you for looking into this ❤️ looking at the table, it actually says None for all records. IIRC, this is an incremental table right? so that means, we were always showing None? in the screenshot below, it seems we may need to set our dbt Cloud env variable?

amm I see Can you use the dbt var

account_id

for now? We will rename the env var so it will be supported as well.

oh ok, yes i can try that. could you please clarify where and how the

account_id

variable should be defined or set within our system or codebase? i’m guessing we can just set it in

dbt_project.yml

?

Yes, you can, or just use

--vars

flag when you run the dbt command

@Noy Arie just following up, this worked! thanks so much!!

Happy I could help 🙂 The env var will be renamed on the next dbt package release.