The Explorer standardizes display for greater clarity. Custom HTML tooltips no longer appear on the default map view. They are replaced by a data exploration side panel.
-
Solution: if your tooltips contain calculations or specific code, turn this map into a Page asset (Code editor).
-
Benefit: your map becomes a searchable object with its own usage statistics.
Good news: you can still retrieve the existing HTML tooltip code and reuse it to update your map widgets.
Step 1 : export datasets that use custom HTML tooltips
Use the following API endpoint to generate a CSV export:
https://<your-domain-name>/api/explore/v2.1/catalog/exports/csv?select=datasetid,visualization.map_tooltip_html&where=visualization.map_tooltip_html is not null&apikey=<your-api-key>
Requirements
You’ll need an API key with “Browse all datasets” permission, especially if you want to retrieve:
- restricted datasets,
- private portals content.
What you’ll get
A CSV export listing:
- the datasets that contain custom HTML tooltips,
- the associated tooltip HTML code (so you can copy/paste it into your widgets).
Step 2 : paste the tooltip HTML in your map widget
During the transition, your existing map widget code should keep working by default.
But if you want to edit / maintain the tooltip HTML, paste the snippet you exported inside your
ods-map widget, specifically inside the <ods-map-layer> tag.
How to find which pages/widgets are impacted ?
In the dataset back office, go to the Data lineage tab.
If you see a page creation coming from your dataset with a linked Geographic field, it’s very likely that this page contains a map widget using custom tooltip HTML — and that’s where you should paste the exported snippet.
Questions
If you are unsure where the tooltip is coming from, feel free to contact your CSM or our support team with the following information : your dataset ID, whether the portal is public/private, a screenshot of your map widget structure (redacting anything sensitive).