Error about creating a dashboard with Asset Bundles

[Shun_T]

Hi, I'm Shun from Japan.

I tried to create Databricks Dashboard using Asset Bundles.

But, I got an error message bellow on Web Terminal.

$ databricks bundle deploy
Warn: Failed to load git info from /api/2.0/workspace/get-status
Error: failed to get dashboard "my_dashboard_name" at resources.dashboards.my_dashboard_name in resources/dashboard_sample.yml:4:7
Unable to get dashboard [Some(dashboards/01f0429515d413bda2802b5b8b47dcfd)]. Caused by Node with resource name Some(dashboardsv3/01f0429515d413bda2802b5b8b47dcfd) does not exist.

I searched this error, but I can't find the way to solve this.

Please tell me how to solve this.

If you want more information to understand the situation, tell me please.

[Vasireddy]

Hi @Shun_T ,

The error message you're seeing,usually means that the dashboard you're trying to deploy either doesn’t exist in your Databricks workspace,or the ID/reference used in the YAML file is invalid.

Here are a few steps that should help:

1.Verify if the dashboard ID is correct

The ID `01f0429515d413bda2802b5b8b47dcfd` seems to come from a pre-existing dashboard. Please go to your workspace → Dashboards, and check if this ID is valid (you can see the ID in the URL when opening a dashboard).

If you’re referencing a deleted or incorrect dashboard ID, the deployment will fail.

2.Fix the YAML Reference

In your `dashboard_sample.yml`, make sure your dashboard section looks like this (assuming you're creating a new dashboard):

resources:
dashboards:
my_dashboard_name:
name: "My Dashboard Title"
definition: ./dashboards/my_dashboard_definition.json

But if you're referencing anexisting dashboard, you should use the exact path or ID:

resources:
dashboards:
my_dashboard_name:
id: "01f0429515d413bda2802b5b8b47dcfd"

Or in some cases:

resources:
dashboards:
my_dashboard_name:
path: /Users/your.name@databricks.com/My Dashboard

3.Permissions

Ensure that your user or service principal hasViewer/Editor access to the dashboard you're referencing.

4.Clear & Retry

Sometimes the local metadata or cache might get out of sync. Try running:

databricks bundle validate
databricks bundle deploy --force