We need the ability to control what is and isn’t visible on the Explore page such as the default map and fields on the data table (don’t delete, just hide so the fields can be referenced by pages/dashboards elsewhere). Having a ‘front and centre’ chart on this page would also be useful and save additional clicks.
This is all functionality/flexibility we had and have now lost.
This follows on from the conversation:Â Default Map View | Community
Open
Ability to control what is / isn't visible on the Explore page
+3Hi @rebecca.flack,
Reading through your points again, I think they all point to the same underlying need: as a data publisher, you want to control the experience your users have — which columns are shown, what the map looks like, what chart is highlighted. That's an editorialized experience, and Custom Views are built exactly for that.
Explore is intentionally raw — designed for users who want to dig into the data directly, without curation. That philosophy isn't going to change.
The good news is that you can already set a Custom View as the primary call to action on your assets, pushing Explore to the background. If your curated view is the experience you want users to land on, that's available today.
Going further, Default Asset Settings will let publishers rename or hide CTAs entirely — so if you want Explore completely out of the picture on certain assets, that will be possible.
Benwa
Login to the community
No account yet? Create an account
Already have a Huwise account ?
Log in with Huwiseor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.