[Core] Explain how using the graph does (or doesn't!) affect the visualization of the DAG

[dbeatty10]

Link to the page(s) on docs.getdbt.com requiring updates

Maybe one or both of:

• https://docs.getdbt.com/reference/dbt-jinja-functions/graph
• https://docs.getdbt.com/reference/dbt-jinja-functions/execute

Tell us more about this update

The big idea is that there's a scenario in which a node can be missing in the visualization of the DAG in dbt Explorer but actually work as intended when building a dbt model. But it's actually not a bug! 🤯

i.e., the compiled query reflects all the intended references but the generated docs is missing some or all.

One of the ways this can happen is when using the graph in the transformation code for a model (like here).

In that scenario, users can compile and run models that use ref and source macros but without those references being reflected in the visualization of the DAG in dbt Explorer or the generated documentation website.

This can be surprising, so we want to explain it the best we can.

---

A suggested improvement would be to show or discuss an example similar to dbt-labs/dbt-core#10665, either within the graph or execute documentation pages.

And/or add a section that could illustrate all the caveats of graph (by comparing when execute==False and execute==True).

Reviewers/Stakeholders/SMEs

Dougie Fresh 😎

Related GitHub issues

dbt-labs/dbt-core#10665

Additional information

No response