Skip to main content
On dbt™ 2.0, Paradime resolves cross-project references itself. A producer workspace turns on Publish public models to other workspaces, and a consumer project lists the producer in dbt™‘s own dependencies.yml. You don’t need dbt-loom, an API key, or environment variables. Workspaces on dbt™ 1.7 to 1.12 keep using dbt-loom. See Configure cross-project dependencies.
Prerequisites
  • The producer and consumer workspaces belong to the same Paradime company.
  • The consumer workspace runs dbt™ 2.0 (2.0-latest, the dbt Fusion engine).
  • The producer project sets access: public on the models you want to share.
  • The Admin, Workspace Settings Admin, or Workspace Admin role in the producer workspace, to turn on publishing.
Cross-project references on dbt™ 2.0 aren’t available to every company yet. If the setting doesn’t work for your workspaces, contact Paradime support.Estimated time: 5 minutes.

​
Steps

1

Turn on publishing in the producer workspace

  1. In the producer workspace, go to Workspace Settings > General.
  2. On the Publish public models to other workspaces card, pick a Publishing environment. You can pick any Bolt environment, or Default environment.
  3. Turn on the toggle.
Consumers see the models from the latest successful run on the publishing environment. Until one run finishes there, nothing is published.Only model names and locations are shared, never SQL. Publishing is off by default, and every change is recorded in your audit logs.
2

List the producer in the consumer project

In the consumer project’s repository, list the producer project in dependencies.yml, next to dbt_project.yml. Use the producer’s project name from its dbt_project.yml:
dependencies.yml
3

Reference the producer's models

Use a two-argument ref with the producer project’s name:

​
How it works

Before each dbt™ command that resolves references, such as dbt run, dbt build, dbt compile, dbt test, and dbt show, Paradime fetches the latest publication of every project in dependencies.yml. This happens in Bolt, in the Code IDE terminal, and when you compile SQL in the Code IDE. The fetch doesn’t need Paradime State. If Paradime can’t reach the publication, the command uses the last copy it fetched and prints a warning. The producer’s card lists the consumer workspaces that recently used its publication, under Recently consumed by.

​
Troubleshooting

  • upstream project '...' is not available to this workspace: the producer workspace hasn’t turned on Publish public models to other workspaces, or no workspace in your company builds a project with that name. Ask the producer workspace’s admin to turn the setting on, and check the name in dependencies.yml.
  • The card shows Not publishing: the publishing environment was deleted. Pick another environment.
  • A model you made public doesn’t resolve: the publishing environment hasn’t had a successful run since you made it public. Run a schedule on that environment.