dosubot[bot] commented on issue #37551: URL: https://github.com/apache/superset/issues/37551#issuecomment-3818236376
<!-- Answer --> In Superset 6, embedded dashboards now enforce stricter checks on dataset metadata and Row Level Security (RLS) rules. If a column like contract_document_number is referenced in a filter, RLS clause, or dashboard slice, it must exist in the dataset metadata and the underlying table or view. Any mismatch will cause SQL errors like the one you're seeing. This is a change from v5, where these checks were less strict. Here’s what to check: - Make sure contract_document_number exists in the underlying database table or view. - In Superset, open the dataset used by your dashboard and confirm contract_document_number is listed as a column. If not, use the “refresh columns” option in the dataset editor. - If you use RLS filters or Guest Tokens for embedded dashboards, verify that any RLS clause referencing contract_document_number is valid and the column exists in the dataset. - After making changes, re-save the dataset and affected charts to update metadata. If the problem persists, enable debug logging and inspect the full SQL query Superset generates to see exactly where the column reference fails. This new behavior is due to the refactored embedded dashboard and Guest Token logic in v6, which requires all referenced columns to be present and correct in the dataset metadata and database schema. More details on this change are available in the [Superset v6 code and PRs](https://github.com/apache/superset/pull/37395). <!-- 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/94fea3f9-eaf8-4447-988a-4b897f5ffe56?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/94fea3f9-eaf8-4447-988a-4b897f5ffe56?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/94fea3f9-eaf8-4447-988a-4b897f5ffe56?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/94fea3f9-eaf8-4447-988a-4b897f5ffe56?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/94fea3f9-eaf8-4447-988a-4b897f5ffe56?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/94fea3f9-eaf8-4447-988a-4b897f5ffe56?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/94fea3f9-eaf8-4447-988a-4b897f5ffe56?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=In%20Superset%206%2C%20embedded%20dashboards%20now%20enforce%20stricter%20checks%20on%20dataset%20metadata%20and%20Row%20Level%20Security%20%28RLS%29%20rules.%20If%20a%20column%20like%20contract_document_number%20is%20referenced%20in%20a%20filter%2C%20RLS%20clause%2C%20or%20dashboard%20slice%2C%20it%20must%20exist%20in%20the%20dataset%20metadata%20and%20the%20underlying%20table%20or%20view.%20Any%20mismatch%20will%20cause%20SQL%20errors%20like%20the%20one%20you%27re%20seeing.%20This%20is%20a%20change%20from%20v5%2C%20where%20these%20checks%20were%20less%20strict.%0A%0AHere%E2%80%99s%20what%20to%20check%3A%0A-%20Make%20sure%20contract_document_number%20exists%20in%20the%20underlying%20database%20table%20or%20view.%0A-%20In%20Superset%2C%20open%20the %20dataset%20used%20by%20your%20dashboard%20and%20confirm%20contract_document_number%20is%20listed%20as%20a%20column.%20If%20not%2C%20use%20the%20%E2%80%9Crefresh%20columns%E2%80%9D%20option%20in%20the%20dataset%20editor.%0A-%20If%20you%20use%20RLS%20filters%20or%20Guest%20Tokens%20for%20embedded%20dashboards%2C%20verify%20that%20any%20RLS%20clause%20referencing%20contract_document_number%20is%20valid%20and%20the%20column%20exists%20in%20the%20dataset.%0A-%20After%20making%20changes%2C%20re-save%20the%20dataset%20and%20affected%20charts%20to%20update%20metadata.%0A%0AIf%20the%20problem%20persists%2C%20enable%20debug%20logging%20and%20inspect%20the%20full%20SQL%20query%20Superset%20generates%20to%20see%20exactly%20where%20the%20column%20reference%20fails.%20This%20new%20behavior%20is%20due%20to%20the%20refactored%20embedded%20dashboard%20and%20Guest%20Token%20logic%20in%20v6%2C%20which%20requires%20all%20referenced%20columns%20to%20be%20present%20and%20correct%20in%20the%20dataset%20 metadata%20and%20database%20schema.%20More%20details%20on%20this%20change%20are%20available%20in%20the%20%5BSuperset%20v6%20code%20and%20PRs%5D%28https%3A//github.com/apache/superset/pull/37395%29.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/37551) -- 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]
