dosubot[bot] commented on issue #37113:
URL: https://github.com/apache/superset/issues/37113#issuecomment-3747684877

   <!-- Greeting -->
   Hi @tejasshah-MK! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping 
the superset team.
   
   <!-- Answer -->
   Exporting a dashboard should include all charts, datasets, and 
databases—even if the charts use datasets from different database connections. 
The export logic recursively collects all related assets: 
ExportDashboardsCommand gathers the dashboard’s charts, ExportChartsCommand 
exports each chart and its dataset, and ExportDatasetsCommand exports the 
dataset and its associated database YAML files. If the new chart and database 
YAML files are missing from your export ZIP, it likely means the dashboard’s 
chart references (slices) aren’t being tracked or exported correctly in the 
backend or UI. You may want to double-check that the new chart is fully 
associated with the dashboard and its dataset before exporting, and review the 
logs for any errors during export. If everything looks correct in the UI, this 
could be a bug in how Superset tracks or exports newly added charts from 
different databases. For more details, see the relevant export implementation 
in the codebase:  
   - [Dashboard export 
logic](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/dashboard/export.py#L108-L224)
   - [Chart export 
logic](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/chart/export.py#L40-L114)
   - [Dataset and database export 
logic](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/dataset/export.py#L40-L126)
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/2f0613a9-2b18-4483-a639-fb1b718df112?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/2f0613a9-2b18-4483-a639-fb1b718df112?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/2f0613a9-2b18-4483-a639-fb1b718df112?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/2f0613a9-2b18-4483-a639-fb1b718df112?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/2f0613a9-2b18-4483-a639-fb1b718df112?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/2f0613a9-2b18-4483-a639-fb1b718df112?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/2f0613a9-2b18-4483-a639-fb1b718df112?feedback_type=other)</sup>
   
   [![Chat with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&nbsp;[![Open
 in 
Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Exporting%20a%20dashboard%20should%20include%20all%20charts%2C%20datasets%2C%20and%20databases%E2%80%94even%20if%20the%20charts%20use%20datasets%20from%20different%20database%20connections.%20The%20export%20logic%20recursively%20collects%20all%20related%20assets%3A%20ExportDashboardsCommand%20gathers%20the%20dashboard%E2%80%99s%20charts%2C%20ExportChartsCommand%20exports%20each%20chart%20and%20its%20dataset%2C%20and%20ExportDatasetsCommand%20exports%20the%20dataset%20and%20its%20associated%20database%20YAML%20files.%20If%20the%20new%20chart%20and%20database%20YAML%20files%20are%20missing%20from%20your%20export%20ZIP%2C%20it%20likely%20means%20the%20dashboard%E2%80%99s%20chart%20references%20%28slices%29%20aren%E2%80%99t%20being%20tracked%20or%20exp
 
orted%20correctly%20in%20the%20backend%20or%20UI.%20You%20may%20want%20to%20double-check%20that%20the%20new%20chart%20is%20fully%20associated%20with%20the%20dashboard%20and%20its%20dataset%20before%20exporting%2C%20and%20review%20the%20logs%20for%20any%20errors%20during%20export.%20If%20everything%20looks%20correct%20in%20the%20UI%2C%20this%20could%20be%20a%20bug%20in%20how%20Superset%20tracks%20or%20exports%20newly%20added%20charts%20from%20different%20databases.%20For%20more%20details%2C%20see%20the%20relevant%20export%20implementation%20in%20the%20codebase%3A%20%20%0A-%20%5BDashboard%20export%20logic%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/dashboard/export.py%23L108-L224%29%0A-%20%5BChart%20export%20logic%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/chart/export.py%23L40-L114%29%0A-%20%5BDataset%20and%20database%20export%20logic%5D%28https%3A//github.com/
 
apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/dataset/export.py%23L40-L126%29)&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/37113)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to