GitHub user kirmorozov1992 added a comment to the discussion: Failed datasources/dashboards import
> A similar issue was reported and resolved by examining the HTTP response JSON > in the browser's debugging console. The error was related to incorrect values > assigned to the `template_params` parameter during the export. The solution > involved unzipping the exported dashboard file, searching for the problematic > field in the YAML files, and replacing the value `''` with `null` for > `template_params`. After compressing the directory back into a zip file, the > import was successful [[1]](https://github.com/apache/superset/issues/26130). > > In your case, the error might be due to validation errors in the metadata or > configuration files within the zip. Ensure that: > > * The zip file contains a valid metadata file. > * All configuration files within the zip adhere to the expected schemas and > contain valid data. > * The file format is compatible with one of the supported import command > versions. > > If the error persists, review the specific validation errors provided in the > exception message to identify and correct the issues in the zip file contents > [[2]](https://github.com/apache/superset/blob/master/superset/commands/importers/v1/assets.py). > > _To continue talking to [Dosu](https://dosu.dev), mention > [@dosu](https://github.com/dosu)._ > > Help Dosu learn! Give it feedback: [Great > Response](https://app.dosu.dev/response-feedback/d44e5d64-dc72-412a-b7e9-3d337a5caa53?feedback_type=great_response) > | [Irrelevant > Answer](https://app.dosu.dev/response-feedback/d44e5d64-dc72-412a-b7e9-3d337a5caa53?feedback_type=irrelevant_answer) > | [Incorrect > Sources](https://app.dosu.dev/response-feedback/d44e5d64-dc72-412a-b7e9-3d337a5caa53?feedback_type=incorrect_sources) > | [Too > Verbose](https://app.dosu.dev/response-feedback/d44e5d64-dc72-412a-b7e9-3d337a5caa53?feedback_type=too_verbose) > | > [Hallucination](https://app.dosu.dev/response-feedback/d44e5d64-dc72-412a-b7e9-3d337a5caa53?feedback_type=hallucination) > | [Bug > Report](https://app.dosu.dev/response-feedback/d44e5d64-dc72-412a-b7e9-3d337a5caa53?feedback_type=bug_report) > | > [Other](https://app.dosu.dev/response-feedback/d44e5d64-dc72-412a-b7e9-3d337a5caa53?feedback_type=other) It is strange. Why should I watch every file and search some value? It is ok, if I have a few objects. But what if I have thounsands of charts and datasets. I want to extract one big package and import it to another superset instance. If package has broken objects, it is good to pass thas, that is all. I noticed that the import error occurs when some chart doesn`t have parent dataset (dataset was deleted), for example. It would be good, if the import process pass that and continue. GitHub link: https://github.com/apache/superset/discussions/34148#discussioncomment-13745365 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
