Product updates

Forms are evolving.💫 You can now customize URLs by adding specific attributes to automatically pre-fill certain form fields. This makes it easy to adapt your forms to each audience or context, while preventing users from re-entering information you already have.         For example, you can send a dedicated link to each department in your organization with the relevant field already pre-filled. Users only need to complete the rest of the form.  👉 To send a form with a customized URL, open any form and head to the “Share” section at the bottom of the page.  

 In the legacy version of the platform, it is possible to provide a simplified view of your datasets (by hiding or reordering fields).However, these adjustments are purely visual: hidden fields remain accessible via exports and APIs, which can lead to confusion.   📆 August 31: full deprecation of table view configurationThe table view configuration will be deprecated (whether you are using the legacy or the new platform experience). The table view will automatically reflect your dataset schema (same fields, same field order). As a result, explored, exported, and queried data will be fully consistent. ✅ 📆 June 23: switch to ‘read-only’ mode for the current configuration (intermediate step)You will no longer be able to edit it, but it will remain visible in your back office as a reference (the change will take full effect on August 31).👉 Preview of your back office on June 23, depending on your setup:Case #1 - you are on the legacy experience (or have only migrated your back office to the new experience):            Case #2 - you are on the new experience (back office and front office):             3 ways to keep providing simplified views 🚀1. Update your schema: align it with your current table view (reordering or removing fields)          2. Configure the dataset “Security” tab: define field visibility based on users or groups            3. Create custom views (new experience only): design table views with filtered, sorted, or limited columns. The full schema-based view remains available, but you choose which one to highlight             Need more information? Check out the documentation. 

When inviting a user, you now have more flexibility over the temporary access you grant them.          Custom duration: enter the exact number of days or weeks of your choice, without being limited to predefined options. Scheduled access: plan a start date so that access begins automatically at the right time.👉 Learn more 

Are you using SSO authentication on your portal? Discover two new features to take your user management further.1. Add access rules based on user attributes to determine whether a user is authorized, denied, or requires approval from a portal administrator.👉 Learn more2. Create and customize access lists based on specific criteria (email addresses, SIRET numbers, INSEE codes, IP addresses, or free-text values) to precisely define which users can access your portal.👉 Learn more

"Data product" is a term you've probably increasingly heard over the past few months. In an article, at a conference… or perhaps even within your own organization.But concretely, what is a data product? How does it differ from a simple data asset? And most importantly, how can you showcase it in your Huwise portal? What sets a data product apart from a simple data asset? High usage 📈: widely and regularly consumed by users Careful packaging 📦: enriched with associated resources to make it more readable, engaging, and actionable Stronger trust ✅: includes an identified, accessible data product owner, and clear commitments through a data contract (SLA, update frequency) Ready-to-use data ✨: adapted formats, enriched views, and business-focused structure to foster user independence and self-service👉 In short, a data product is a high-usage data asset, comparable to a best selling item on an e-commerce site: it captures attention, requires ongoing care and engaging presentation (just like a real product) to sustain its success over time. 🌟 Key features to turn your data assets into data products 📦 Visibility: highlight your data products in a dedicated category with a thumbnail to make them easier to spot.     Context: enrich entries with associated resources (prepared views, business definitions, data contract, use cases).      Scalability: continuously improve usage through conversion funnel insights.     

A data catalog should not simply be a list of technical assets. It should become an engaging showcase that helps business users easily discover, understand, and leverage the right data products.        👉 Discover three practical ways

 Discover the new "Explore data" view, a space designed to enable your users to manipulate data in just a few clicks and iterate freely!          👉 Practical informationIt is a modernized version of the “Analyze” tab, with a stronger focus on data exploration (learn more) This feature will be visible to your users only if the new Huwise experience is enabled on your portal (learn more)🚀 What’s new for your users (compared to the “Analyze” tab)Clearer, more modern filters Direct access to the dataset schema The ability to remove a test in one click Able to switch visualization formats in one click

You can now display buttons directly on your catalog cards, enabling users to take action in one click based on their needs: explore data instantly or access the product page for more context.         Practical information This feature is only available within the new platform experience. Contact your Customer Success Manager to activate it (learn more) To display buttons in your catalog, go to your Back Office > Settings > Catalog Page > Conversion objective button

Are your datasets too large or too sensitive to be moved from their original source?    With “zero-copy” sharing, they become directly accessible from your portal while remaining physically at the source - without duplication. 🎉         The benefits of zero-copy sharing Broader usage: business teams can independently explore data through the portal, without needing to master SQL queries. Discoverability: data can be enriched with additional portal-specific metadata to improve understanding and ease of discovery. Reliability: data can be accessed in the portal while remaining synchronized with its source and retaining its status as the single source of truth. Security: data benefits from the same level of protection as queries performed on traditionally shared datasets. Learn moreCheck out our documentation or fill out this form to be contacted by our team.

Want to reveal the full potential of your data to your users?Discover Huwy, the AI exploration agent that transforms data discovery into a simple, intuitive, and instant experience.         👉 Learn more

What if your users had all the context they need to explore your data independently?From now on, your data presentation pages automatically display the source and associated usages. A simple way to build trust in your data, while helping your users understand how it’s being used… and inspiring them to imagine new ways to leverage it!         In short, your users can easily access data lineage information, presented clearly and intuitively for them.Practical informationYou can disable the display of certain sections depending on their relevance to your data. Learn more  This feature is only available in the data marketplace. Contact your Customer Success Manager to enable it. Learn more

Using SSO authentication? You can now configure multiple OpenID Connect (OIDC) providers to connect to your portal — ideal if you manage several entities 🤝    This update introduces modernized interfaces, allowing you to manage your SAML and OIDC providers independently, and navigate more easily thanks to the new “Configuration” and “Group mapping” tabs.      👉 To explore these new interfaces, go to Back office > “Access” tab > “SSO” tab, and check out the user documentation to learn more.

Our form feature is evolving to make it easier for you to ensure that the data users provide is accurate and high quality. This update aims to make your forms more dynamic and collaborative, while maintaining a high level of control and consistency. 🎉👉 Two ways to edit contributionsBefore publication (as an administrator): you can correct, standardize, or complete submissions before approving them, safeguarding your dataset’s overall quality and consistency.After approval (by users): once their contributions have been approved, users can correct or update their responses through an edit link available in the published dataset on your portal.   🔧 Enable this setting: Simply click the “Let users propose changes” option in the “Actions” menu of the form feature. 📚 Learn moreCheck out our dedicated user documentation, contact your Customer Success Manager, or ask your questions directly in this Community post.

A few months ago, we introduced the new join processor, designed to handle joins on large datasets with no size limits.          On November 30, all joins using the old processor will be automatically migrated to the new one, which will permanently replace it.Recommended actions before November 30 ⚠️ Automatic migrations by Huwise will trigger a full reprocessing of the affected datasets at their next manual or scheduled publication. If you have datasets that are updated regularly and require a long processing time, we recommend anticipating the automatic migration by updating your joins with the new processor now. We’re here to help if you need support. Since the new processor does not behave exactly the same as the old one due to the improvements made, we encourage you to check how it works on your datasets using older joins, especially those with keys starting with “0.” If you notice differences in results with the new join, you can adapt your data by adding back the missing leading zeros. If you use spreadsheet tools (Excel, etc.) to prepare your data, make sure to format your codes as “text” to avoid losing the leading zero. Have questions or need help?Reach out to your Customer Success Manager or post your questions directly on this Community post. We’ll be happy to respond and guide you through the process. 

After 14 years, our brand is evolving! New name, new colors, new identity… but the same solution and the same mission: helping you turn your data into a source of knowledge, innovation, and performance.         A new name that reflects our visionHuwise = Human + Wise: enhancing human thinking through data. New identity, same platformDon’t worry - the platform works exactly the same as before. Only a few visual elements have changed to reflect our new identity: the logo, the name in the portal footer, login screens, etc. Learn more Watch the video from our co-founders and check out our FAQ to get all the details about the change!

What is the Automation API?The Automation API streamlines the back-office management of an Opendatasoft portal by automating over 150 actions—from data publication to domain and user permissions management—without using the interface.      New endpoints to manage your metadata translationsAutomatically set translations for your metadata with the new Automation API endpoints. No need to re-enter them manually if they already exist in your information system tools or within the portal. The result: significant time savings and simplified multilingual management.Try it nowIf your plan includes the Automation API, you can now explore the updated technical documentation to try it out:Translation suggestions Code editor pages translations Studio pages translations Dataset translationsLearn moreDiscover real-world use cases and the benefits of the Automation API in this dedicated article Contact your Customer Success Manager or sales representative

 What is a geographic reference dataset?A geographic reference dataset is a dataset describing the administrative divisions of a country or area.     What new reference datasets are available?Reference datasets for Switzerland:Cantons Municipalities (Gemeinde) Districts (Bezirk) Postal codes (4 digits) Postal codes (6 digits)Reference datasets for the United Kingdom:Output Areas (new dataset) Local Authority Districts Lower Layer Super Output Areas Counties & Unitary Authorities Middle Layer Super Output Areas Regions Countries Parishes & Communities Wards & Electoral Divisions

Good news! You can now easily duplicate your blocks and pages in the no-code studio, providing a valuable time-saver to speed up creation of your pages and data visualizations!👉 To duplicate a page:Go to your back office Go to the Pages Editor section > Studio Create a page, or open an existing one Click the Duplicate icon: 👉 To duplicate a block in a page:Still in the Studio, open the page of your choice Hover over the block you want to duplicate  Click the Duplicate icon:       Note: a section can only contain 4 blocks. If the limit is reached, the duplication option is disabled (to duplicate a block, first drag and drop it into another section). 

Have you activated all the latest features released on your Opendatasoft portal in 2025? Catch up with our summer recap to stay fully up to date before the new season—especially if you missed our latest newsletter. 📮🇫🇷 Newsletter recap (FR) 🇬🇧 Newsletter recap (EN)

They are now fully compatible with the latest version of DCAT-AP-CH (v2) and its recent updates.🚀 By using this metadata template, your portals will be fully harvestable by opendataswiss, the Swiss national portal. Indeed, opendataswiss has recently updated its metadata validation system in line with DCAT-AP-CH v2.⚠️ Until opendataswiss migrates to opendata.swiss next (planned for 2026), importing non-compliant metadata on opendataswiss will remain possible but will trigger error emails. We therefore recommend updating your DCAT-AP-CH metadata now for optimal harvesting.💡 What should you pay particular attention to?opendataswiss checks are now more thorough. All mandatory metadata must be present and accurate. The compliance of recommended and optional properties, if provided, is also checked. Make sure to review the completeness and accuracy of your metadata.  the dct:license metadata replaces dct:rights. The dct:license metadata refers to the terms of use of datasets on opendataswiss. It is mandatory and can only take four values (defined here). We have integrated this new metadata into our Opendatasoft DCAT-AP-CH template, and you can directly choose from the four possible values in the back office. the dct:rights metadata now serves to specify the dataset’s license only in the specific case where it falls under one of the three Creative Commons licenses defined here. The dct:rights metadata is displayed when the dataset is published on data.europa.eu but not on opendataswiss. In the Opendatasoft DCAT-AP-CH export, dct:rights will be generated from the license metadata in the Dataset template, if it matches one of the three allowed CC licenses. The former dct:rights field in the Opendatasoft DCAT-AP-CH template is deprecated and should no longer be used.📖 ResourcesFor full details on the DCAT-AP-CH v2 template, see the official documentation. For full details on the metadata validation system implemented by opendataswiss, see their handbook.

From September 30, our extraction system for FTP and SFTP sources will be updated to ensure better consistency between your published datasets and their original source.🔎 What’s changingCurrently, extracted files are cached even if they are deleted from the source. With the new process, only files that are present in your external source at the time of republishing will be kept. Deleted files will no longer be retained in Opendatasoft.👉 Actions to take before September 30If there are deleted files still stored in your cache, you can:Keep them by adding them back to your source, or by exporting your current dataset and reintegrating it into the source. Permanently delete them by clearing the cache for the relevant datasets, starting from a clean slate.         🚀 Benefits of this updateFaster and smoother loading in the back office Data is always aligned with your external source Improved traceability of extraction errors💡 Need help?Contact your Customer Success Manager, our Support team. 

The form feature keeps evolving to offer you more flexibility and improve the quality of collected data:           👉 Learn moreHaven’t created a form yet? A free form is still included by default. Just ensure the “forms” permission is enabled in your back office to access the feature. 🙌 

The previous limit of 100,000 records is gone!Enrich your data now using large datasets with large reference datasets such as France’s SIRENE (a directory of ID codes for every business in the country)— without compromising performance!        👉 To try out the new processor, check the user documentation.👉 To understand potential impacts, watch this video.

Multi-factor authentication is now available and complements existing security mechanisms to enhance the protection of your portal!          👉 Enable MFA now

In a few days, you'll be able to perform joins on very large datasets with no size limit. 🎉     👉 To help you prepare for this change, you’ll receive an email with the list of affected datasets and the actions to take. Stay tuned!