Huwise discussions

Hi everyone,How to make your data easier to explore on your Huwise portal?  Here are the main points with few portals examples.1. Use the 3-30-300 rule to size each visual ⏱️Each visual should match the time your user will spend on it:3 seconds: one key message. A title, a number, a color. The user decides if the data concerns them. 30 seconds: a chart with axes, a legend and 2–3 filters. The user understands a trend or a distribution. 300 seconds: several linked visuals with context. The user understands the full story and can make a decision.A quick test: show your visual to a colleague who doesn’t know the topic for 3 seconds. What do they remember?2. Start with native custom viewsCustom views let you create up to seven views per dataset, with no setup beyond a few clicks:Key figure: for the 3-second level. Example: unemployment rate on the North Carolina OSBM portal. You can export it as PNG. Map: for any data with a location. Example: public finance offices on the French Ministry

We’re currently trying to navigate the new interface in the back office.  There is a filter we were using on a daily basis which we cannot see/find.We used to be able to filter for Last modified and date range:The new experience provides only a single date for selection -- could you reinstate the ability for a range to be selected?   

Hi everyone,On a portal with dozens or hundreds of assets, finding the same dataset again takes time. You have to re-type the search, re-apply the filters and scroll through the cards. Bookmarks remove that step. Here is how they work and how data explorers and data owners can use them.How it worksYou can bookmark an asset from two places:In the catalog: each asset card has a bookmark icon. Click it to save the asset while you browse, without opening the asset page.On a dataset's Explore page: the Bookmark button sits in the top-right corner, next to Export data, Use API console and Show views.All your saved assets are in Account > Bookmarks.Two conditions apply:You must be logged in with an account. The Bookmark button does not appear for anonymous visitors. You can bookmark any asset you have access to. Some assets are visible in the catalog but restricted to specific users. For those, the asset page shows a Request access button, and the publisher decides whether to grant access.

I think I remember that in the legacy experience, in the Table view, if you mouse hovered over the field (column) heading, the field’s Description metadata would appear. This was and would be quite useful for fields which are defined in complex or ambiguous ways, so that the user can quickly understand the derivation of the values and the meaning of the data.Currently in the marketplace experience, hover over the field names just reproduces the name. Could it be changed (back) to show the description?cheerssteve

Have you ever seen an "Alert detected during processing" message when trying to publish a dataset? Or maybe a colleague reported missing rows in a dataset that published without throwing a hard error?When a dataset hits a limit during processing, publication can either fail completely or stop partway, leaving some of your data or sources out. Here is a quick breakdown to help you identify the cause and get your dataset published.🔍 1. First, check the message typeBefore diving into troubleshooting, check how the error begins in your back office (Asset Settings or Content page): Alert detected during processing: follow the steps below! This means a quota, workspace setting, or platform threshold was reached. Error during processing: this is not a quota issue. Check if your source URL/file is reachable or if the schema/structure changed. 💡 Email vs. Back Office: email alerts tell you a limit was reached, but not which one. Always check the message inside the dataset’s back-office page

Hey everyone 👋A question that comes up now and then: "To connect my third-party harvester (a regional geoportal, data.gouv.fr, a GIS platform...) to a Huwise portal, what do I actually need ? An API URL, a DCAT metadata URL... both?"The answer that tends to surprise people: it's the same URL. The catalog's DCAT export covers both roles at once:https://your-portal.example.com/api/v2/catalog/exports/dcatThat single address is enough to reference the entire catalog in any DCAT-compatible harvester, whatever tool sits on the other end.Want to go further:📘 The step-by-step guide (originally written for data.gouv.fr, but the method holds for any third-party DCAT harvester): Referencing your datasets on data.gouv.fr 🛠️ The full API reference (available parameters, DCAT-AP formats you can enable on request, authentication): Catalog DCAT export docsSo, who here has already hooked up an external harvester to their Huwise portal? Curious to hear your setups 👇

Hello,When browsing a dataset, I would like to modify / update the map based on Explore by query settings. ExampleI’ve filtered to any record greater than 5MW, but I’d like to see that change reflected in the map tab. Thanks!

Is there a dataset you'd love to see on the Huwise Data Hub? Or maybe an existing dataset that deserves more frequent updates, extra fields, or a fresh enrichment?We've made it easier than ever to let us know.A dedicated data request form, accessible directly from the Hub's top menu (Data > Data request), lets you tell us exactly what you need:Request an update to an existing dataset Request a brand-new dataset that would be useful for your projects Share context on why it matters to you, so we can prioritize accordingly🔗 Submit your request hereWe read every submission. Don't hesitate to share your ideas, use cases, or "wish list" datasets in the comments below too.

Hey everyone! 👋We’re excited to highlight a new feature designed to help you unify your analytics and data assets: the Tableau Harvester.If your organization uses Tableau alongside Huwise, you no longer have to worry about fragmented data portals or sending users back and forth across different links. With the Tableau Harvester, you can surface your Tableau dashboards right inside your Huwise marketplace, giving your teams a unified, embedded experience!💡 What does the Tableau Harvester do? Embedded experience: users can interact with live Tableau dashboards directly in the Huwise portal. No external redirects or extra tabs required. One asset per dashboard: the harvester automatically imports each Tableau dashboard as a dedicated asset into your Huwise catalog. Metadata mapping: attributes like dashboard titles, descriptions, owner contact info, tags, and thumbnails automatically map over to Huwise (and you can customize custom metadata mappings, like listing "Data sources used"

If you're a Catalog Curator or Admin, you know the tension: users want more data in the marketplace, but every new dataset means more storage, more sync jobs, more staleness risk, and more governance overhead to track. Zero-copy (virtualization) removes a big chunk of that burden.What it solves for youNo duplication to manage. Zero-copy assets keep their records in the source system (Snowflake or Databricks). You expose the data without ingesting and storing a copy in Huwise : one less thing to maintain, monitor, and pay for. Data is always current. Because exploration queries hit the source directly, there's no sync schedule to configure, no "last updated" gap to explain to users. What they see in the marketplace is what's in the warehouse, right now. Governance stays exactly where you expect it. Zero-copy assets go through the same publication workflow as any other harvested asset : nothing is published automatically, so you still review before making it live. Access control and secu

Hello,I'd like to update the metadata for the assets using the Automation API. It seems that not all metadata fields can be modified directly via the API.Where can I find these restrictions?Using `/automation/v1.0/metadata/templates/default/fields`, you can see all fields, including those that cannot be modified.Furthermore, it’s not possible to retrieve the values of a list, such as for `default.theme`. 

Huwise now ships several AI building blocks, each built for a specific purpose. Knowing them well means picking the right tool for the right moment. Here's a quick tour.1. AI Insights: turn a question into a chartWhat it is. AI Insights generates a chart on the fly from a question asked in plain language, with no prior configuration. You describe what you want to visualize ("breakdown of data assets by topic"), and the AI identifies the relevant fields among the assets you have access to, picks a suitable chart type, and displays it.Why it's useful. For a one-off need : prepping for a meeting in ten minutes, checking a hunch, exploring data with no technical skills required. AI Insights skips manual configuration entirely. Good to know. The result is disposable: if you need a stable chart to share or reuse over time, use Chartbuilder instead, not AI Insights. And as with any generated answer, always double-check the numbers shown against the relevant data asset's page. 2. Semantic sear

In the past we were able to draw a polygon in a geographical map (e.g. Germany Postal Codes). This was used to extract a specific list of postal codes and areas based on the polygon. Right now it does not seem to be possible to draw those polygons on the map anymore. Is there a way around it or a possibility in the future again? 

If you've ever had a data asset stuck in draft because of one empty mandatory field (and no way to tell which one without opening every record), here's how to fix that programmatically instead of clicking through the UI one asset at a time.Why this happensEvery metadata template defines requirement levels (mandatory / recommended / optional). Soon, you won’t be able to publish an asset if a mandatory field on its active template is empty. Recommended fields never block publication, they just show as a caution sign within the asset settings page.The 3 calls you need :1/ GET the metadata template : returns the list of fields with their requirement level, so you know which ones are mandatory.GET /api/automation/v1.2/metadata-templates/{template_id}2/ GET  the asset's current metadata : returns the values currently set. Compare against the template to spot any mandatory field that's missing or empty.GET /api/automation/v1.2/datasets/{asset_id}/metadata3/ PATCH the asset's metadata : send t

For a spatial dataset, I can add an additional geographic projection e.g. 27700 for BNG in the backoffice. But this doesn’t appear in the export tab as an option, and my testing shows that the export is still in WGS84 - the default. Am I missing something or is this feature not working in the marketplace experience?

Hey thereWhen we want to embed a table in an iframe we have the /embed/ endpoint that we can use to hide the ODS header when displaying the dataset. Here is an example:Table with header:https://data.bl.ch/explore/dataset/12060/table/?disjunctive.jahr&disjunctive.gemeinde&disjunctive.kategorie&disjunctive.einheitTable without headerhttps://data.bl.ch/explore/embed/dataset/12060/table/?disjunctive.jahr&disjunctive.gemeinde&disjunctive.kategorie&disjunctive.einheitWe are currently trying to embed a dashboard created with the studio in an iframe. However, we can’t get rid of the header. Example:Dashboard with header:https://data.bl.ch/p/wahlen_nr_sr/Dashboard without header:? Is there a possibility to achieve this? If yes, how? Many thanks for your helpAuto-translation 🪄Salut. Lorsque nous voulons intégrer une table dans une iframe, nous avons le point de terminaison /embed/ que nous pouvons utiliser pour masquer l'en-tête ODS lors de l'affichage de l'ensemble de d

Hello dear community :)We have created a new visualization here: Veranstaltungen im Raum St. Jakob.This visualization is based on four other datasets, and we would like to reference it. However, we can't find where or how to add this link/reference.Could you please let us know how to add our visualization as a source/usage reference on the four original datasets?Thank you for your help.Best regards,Boris 

Après plusieurs tests de configuration, le support Opendatasoft nous a indiqué que le connecteur HTTP en OAuth2 ne permet pas encore de limiter l’autorisation d’accès à un site SharePoint en particulier “Sites.Selected” (voir Controlling app access on a specific SharePoint site collections - ESPC Conference, 2025). Pour le moment, il est uniquement possible d’accorder une autorisation sur tous les sites SharePoint de notre organisation ce qui n’est pas conforme aux bonnes pratiques de sécurité « least privilege access ».Nous espérons que ce développement sera programmé dès que possible par Opendatasoft. Nous vous remercions d’avance de soutenir ce besoin et de partager votre expérience à ce sujet.Nadia (Ville de Bruxelles)Auto-translation 🪄After several configuration tests, Opendatasoft support informed us that the HTTP connector in OAuth2 does not yet allow to limit the access authorization to a particular SharePoint site “Sites.Selected” (see Controlling app access on a specific Sha

Your data has powerful stories to tell, but if your team or users find it overwhelming, those insights get lost in translation.It’s time to change that.We are hosting a live training webinar on August 27th at 4:30pm (Paris time) designed to help you transform raw numbers into compelling, visually stunning data stories.📊 Make your data irresistible to exploreBuild Visualizations, Dashboards, and Data Stories That Stand OutIn this practical, hands-on session, you will learn how to: Hook your audience:  design layouts that immediately draw the eye to what matters most. Simplify the complex: turn cluttered charts into clean, intuitive, and interactive experiences. Drive action: master the art of "data storytelling" so your stakeholders don't just look at the data—they actually use it to make decisions. 📅 Event Details Where: Online (Grab your virtual seat below!) Who it's for: Data owners and Catalog curators who want to level up their data presentation game. 👉 Click here to secur

Hello community! 👋The new Huwise experience offers many possibilities to help your users visualize and explore your data. To help you choose the right tool depending on your business needs, here is a complete overview—from no-code to custom applications—followed by our usage recommendations. 🗺️ The options matrix: from simplest to most advancedLevel Feature What it enables Who uses it? 1: Automatic Dataset preview (Data/Schema/Map tabs), and soon in the new “Explore” The user generates a table, chart, or map fully independently from the dataset Data consumer 2: Conversational Huwy conversational agent The user asks a question in natural language and gets an instant, tailored visualization Data consumer 3: No-code, per asset Custom view The data producer manually creates charts (bars, lines, pie…), maps, or KPI widgets attached to a dataset—customizable and embeddable on the asset page—to simplify access to the data asset Catalog curator / Data owner 4: No-

dans la vue personnalisée, la légende apparaît systématiquement réduite : je souhaite que la légnde soit systématiquement affichée eau complet sans devoir cliquer sur le terme x éléments de plus quel paramètre dois-je imposer au code html ?merci à vous 

Is it possible to copy the full contents and paste from a field from the table view?  For example the geo_shape when complex truncates.  It would be great if we can copy and paste the whole field.

This week ​@yier.wu  (Customer Support Specialist) and ​@frederic.passaniti (Solutions Architect) have broken down the biggest takeaways, limitations, and clever strategies discussed to keep your data publishing seamless. "Volume limits should never be an obstacle to publishing your datasets." — ​@Nicolas Terpolilli , Head of Product Delivery 📊 Understanding the limitsThe platform enforces three distinct types of technical limits based on how your datasets are ingested:1. Local file uploads (240 MB) The limit: applies to individual source files (CSV, JSON, XLSX, etc.) uploaded directly from your computer. Pro-tip: a single dataset can aggregate multiple sources, meaning you can combine multiple files that are each under 240 MB. 2. Remote connections (500 MB) The limit: applies to remote server data fetches via URLs, APIs, or data warehouse connectors (Snowflake, Databricks, Google Drive, etc.). Watch out: if an API response exceeds 500 MB, you'll receive a transfer error. This can