Data marketplace: What’s new or different?

This page is part of our guide to the new data marketplace experience. You can also see our other pages about what's mandatory to migrate, as well as what's in the pipeline to be released.

The data marketplace upgrade is more than a facelift, it turns your portal into a true catalog of data products.

You can now register any kind of asset (datasets, dashboards, apps, documents, ML models, and more), slot them into curated categories to tell a story, and enrich them with a business glossary that speaks your users’ language.

Each asset can carry its own call-to-action: Request access, Open in Power BI, Download CSV, and so on, guiding users to the next step instead of leaving them guessing.

Behind the scenes, an enhanced analytics funnel tracks every stage of the journey from search, to click, to API calls so admins get a clearer view of what’s working and what isn’t.

We won’t go through the entire feature set here. Instead, this section zeroes in on what feels different compared with the old interface. What has moved? What changed? What was simplified or retired?

The global stylesheet isn’t going away, but anything you can now do in no-code settings has been lifted out of CSS. When activating the data marketplace, you can redesign the catalog theme (layout, buttons, catalog cards) straight from the back office under Portal > Style.

Why the change?

• A more modern UI, always up to date
  Fewer hard-coded overrides mean we can ship interface improvements without breaking your look and feel.

• Admin-friendly maintenance
  No more digging into CSS. Branding tweaks take minutes, not deploys.

• Best-practice personalization
  High-impact options (colors, spacing, badges) are available in the editor; deep custom hacks stay in the stylesheet for edge cases only.

As we add more no-code controls, the stylesheet will cover less and less, keeping your marketplace customizable and upgrade-proof.

As you prepare for activation, make sure to review your current portal: if you’ve added custom CSS for very specific use cases, side effects may occur. Don’t worry, our team will support you in checking and validating these changes to ensure a smooth transition.

See the article in our Community for more details.

Head to Catalog > Settings and you can now:

• Turn any metadata field, standard, custom, or DCAT/interop, into a catalogue filter

• Choose a default sort order for search results

To keep things simple and also because almost nobody used them, the legacy default sorts by "record count," "downloads," and "popularity" have been removed.

The familiar Chart Builder and Map Builder aren’t going anywhere for now, and you can keep using them exactly as before. However, longer term they’ll probably be replaced by a “playground” directly in the portal: end users will be able to create their own visual assets in a private workspace and submit them to an administrator for publication in the catalogue as full showcases, if relevant.

The old “Menu Pages” section is gone: Studio pages and Code editor pages are now full assets, just like datasets.

• They appear in the global Assets list in the back office and inherit the full metadata model, plus the user and group visibility rules.

• Because they now carry metadata, they show up in the portal search and filters. Users can find the right page with a keyword or tag instead of hunting through menus.

• Usage analytics are tracked the same way as for any other asset, so you see exactly how often each page is viewed.

One caveat: the “Last edited by” label is temporarily missing for pages, but it will return once it’s consistent across all asset types.

The one-click “Statistics” button that used to sit next to each dataset is gone.

Analytics are now grouped under the dataset itself:

In the dataset, go to Analytics > Activity.

Same figures, cleaner path designed around how users actually consult usage data today.

The asset page is the bridge between the data marketplace and the underlying data.

It displays the asset’s key metadata in an e-commerce-style layout (title, description, quality, license, similar assets, etc.) so users understand data before they consume it, and administrators decide which calls-to-action appear: Export, Explore, Request access, and so on.

In short, it presents the right context to end-users while giving admins full control over which actions are promoted. Page views, CTA clicks, bounce rate, and conversion funnel metrics are all captured, giving you hard data on what resonates and where users drop off.

There is no change for now, the “dataset of datasets” still behaves exactly as it did in the previous experience. However, it will eventually upgrade into a broader “dataset of assets.”

The portal's Analysis tab has been retired because it overlapped heavily with custom views, confusing editors, and, since it wasn’t treated as an asset, its engagement couldn’t be tracked.

• For admins: If you need a curated chart or table as the landing view, build it with the new custom view feature (there’s no automated migration).

• For end users: A new “playground” tool will soon appear in the portal, letting users create quick visual insights on a dataset—without leaving the data marketplace.

The old “Territory” filter let users pick an area on a map and instantly narrow the catalogue to datasets tagged with that territory. That dedicated filter is no longer available, and we haven’t decided whether to rebuild it in the same form.

A workaround: Add a custom "Territory" metadata field to your datasets and expose it as a standard catalogue filter by going to the back office, then Catalog > Settings. Users will be able to filter by name (not by map).