dosubot[bot] commented on issue #37551: URL: https://github.com/apache/superset/issues/37551#issuecomment-3818324073
<!-- Answer --> In Superset 6, if you use a global RLS clause (by omitting dataset ids), that clause is applied to every dataset in the dashboard. If even one dataset is missing the referenced column (like contract_document_number), every chart using that dataset will fail, and Superset will batch the chart data requests—so a single error can cause all charts to fail with just a couple of 400 responses from /api/v1/chart/data ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/charts/data/api.py#L187-L464), [source](https://github.com/apache/superset/issues/32889)). To resolve this, double-check that every dataset used in your dashboard (including virtual datasets and legacy charts) has contract_document_number in both the dataset metadata and the underlying table/view. Use the "refresh columns" feature in the dataset editor if needed. If only some datasets should have the RLS clause, explicitly specify the dataset ids in your RLS array to avoid applying the clause where the column doesn't exist. Also, make sure your environment matches Superset 6 requirements: Node.js 20+ for frontend builds, all database migrations applied, and clear your browser cache after upgrading ([source](https://github.com/apache/superset/issues/37282)). If you still see 400 errors, check the exact error message and payload in the /api/v1/chart/data responses—this will tell you which dataset or chart is causing the failure. If needed, try isolating the dashboard to a single chart at a time to identify the problematic dataset or configuration. <!-- 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/1c7a743d-d288-403d-b2e3-ede01296dbe4?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1c7a743d-d288-403d-b2e3-ede01296dbe4?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1c7a743d-d288-403d-b2e3-ede01296dbe4?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1c7a743d-d288-403d-b2e3-ede01296dbe4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1c7a743d-d288-403d-b2e3-ede01296dbe4?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1c7a743d-d288-403d-b2e3-ede01296dbe4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1c7a743d-d288-403d-b2e3-ede01296dbe4?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%20if%20you%20use%20a%20global%20RLS%20clause%20%28by%20omitting%20dataset%20ids%29%2C%20that%20clause%20is%20applied%20to%20every%20dataset%20in%20the%20dashboard.%20If%20even%20one%20dataset%20is%20missing%20the%20referenced%20column%20%28like%20contract_document_number%29%2C%20every%20chart%20using%20that%20dataset%20will%20fail%2C%20and%20Superset%20will%20batch%20the%20chart%20data%20requests%E2%80%94so%20a%20single%20error%20can%20cause%20all%20charts%20to%20fail%20with%20just%20a%20couple%20of%20400%20responses%20from%20/api/v1/chart/data%C2%A0%28%5Bsource%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/charts/data/api.py%23L187-L464%29%2C%20%5Bsource%5D%28https%3A//github. com/apache/superset/issues/32889%29%29.%0A%0ATo%20resolve%20this%2C%20double-check%20that%20every%20dataset%20used%20in%20your%20dashboard%20%28including%20virtual%20datasets%20and%20legacy%20charts%29%20has%20contract_document_number%20in%20both%20the%20dataset%20metadata%20and%20the%20underlying%20table/view.%20Use%20the%20%22refresh%20columns%22%20feature%20in%20the%20dataset%20editor%20if%20needed.%20If%20only%20some%20datasets%20should%20have%20the%20RLS%20clause%2C%20explicitly%20specify%20the%20dataset%20ids%20in%20your%20RLS%20array%20to%20avoid%20applying%20the%20clause%20where%20the%20column%20doesn%27t%20exist.%0A%0AAlso%2C%20make%20sure%20your%20environment%20matches%20Superset%206%20requirements%3A%20Node.js%2020%2B%20for%20frontend%20builds%2C%20all%20database%20migrations%20applied%2C%20and%20clear%20your%20browser%20cache%20after%20upgrading%20%28%5Bsource%5D%28https%3A//github.com/apache/superset/issues/37282%29%29.%0A%0AIf%20you%20still%20see%20400%20errors%2C%20ch eck%20the%20exact%20error%20message%20and%20payload%20in%20the%20/api/v1/chart/data%20responses%E2%80%94this%20will%20tell%20you%20which%20dataset%20or%20chart%20is%20causing%20the%20failure.%20If%20needed%2C%20try%20isolating%20the%20dashboard%20to%20a%20single%20chart%20at%20a%20time%20to%20identify%20the%20problematic%20dataset%20or%20configuration.) [](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]
