dosubot[bot] commented on issue #34295:
URL: https://github.com/apache/superset/issues/34295#issuecomment-3111907086
<!-- Answer -->
Your D3_FORMAT config structure is still supported in Superset 4.1.3, and
the backend/frontend pipeline for passing it hasn't fundamentally changed. The
most common cause for custom D3_FORMAT not being applied after an upgrade is
that superset_config.py isn't being loaded—this can happen if it's not in your
PYTHONPATH, has a syntax error, or isn't picked up at runtime.
To debug:
1. Use browser devtools to inspect `window.bootstrap_data.common.d3_format`
(or `window.bootstrap_data` if nested) on any Superset page. If your custom
format isn't there, Superset isn't loading your config.
2. If it's missing, check that superset_config.py is in the correct location
and free of errors. You can also run `superset shell` and check `from superset
import conf; print(conf.get("D3_FORMAT"))` to confirm it's loaded.
3. If your config is present in the frontend but not applied, clear your
browser cache and restart all Superset services to ensure no stale assets are
used.
4. Recent changes in number formatting (especially for table charts) mean
that if a metric's currency config is `{}` (empty object), D3 formatting will
now be applied as expected, but if you have a non-empty currency config, it may
override your D3_FORMAT for that metric. See [PR
#34127](https://github.com/apache/superset/pull/34127) for details.
If you still have issues, check Superset logs for config or serialization
errors, and consider sharing the relevant logs or your bootstrap data snippet
for further diagnosis.
<!-- 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/5ad39200-3467-4091-b101-614ef7381572?feedback_type=great_response)
|
[Irrelevant](https://app.dosu.dev/response-feedback/5ad39200-3467-4091-b101-614ef7381572?feedback_type=irrelevant_answer)
|
[Incorrect](https://app.dosu.dev/response-feedback/5ad39200-3467-4091-b101-614ef7381572?feedback_type=incorrect_sources)
|
[Verbose](https://app.dosu.dev/response-feedback/5ad39200-3467-4091-b101-614ef7381572?feedback_type=too_verbose)
|
[Hallucination](https://app.dosu.dev/response-feedback/5ad39200-3467-4091-b101-614ef7381572?feedback_type=hallucination)
| [Report
🐛](https://app.dosu.dev/response-feedback/5ad39200-3467-4091-b101-614ef7381572?feedback_type=bug_report)
|
[Other](https://app.dosu.dev/response-feedback/5ad39200-3467-4091-b101-614ef7381572?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu
b) [](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/34295)
--
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: notifications-unsubscr...@superset.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
