Option to set hidden columns by default

[Nicki Schermann]

I would like there to be an option to hide some columns by default. Currently I can hide them but as soon as I refresh they come back, and if anyone else visits the database they're also not hidden for them. I would like an option to set the visibility of columns myself - obviously users should still have the option to un-hide columns if they need to.

[Filip Callewaert]

This makes me think of an opportunity to have "restrictions" / "permissions" on "Views". 

[Hendrik Hillus]

Hi Nicki,

I have been able to hide columns "for all" by creating a custom view and making it the default view.

I am currently in Alpha and not sure if this works still the same in Beta. What I did is create a new view, apply all filters and hide the columns. Save the new view and give it a name and then make it the default view

[Rachel Li]

Hi! I'm from the databases team and can confirm that views work the same way in Beta - you can create a new view with hidden columns and set it as the default view.

[Nicki Schermann]

Oh thank you! I would have expected that 'add view' option to live in the same section as where you can hide fields - I didn't notice it over the other side. I appreciate the help!

[Tami Dubi]

Hi @Rachel Li ,

When embedding a data base in a confluence page, the view that is shown afer publishing a page is automatically the entire entry view (or perhaps the defulted view of the data base). The view that we chose when the page was in edit mode wasn't saved as the default of the page (the customs views that are created are not shown as the defult.

Wehn we embedd a data base in a page. there needs to be an option of showing in the Confluence page the view that was chosen in the page editor without the option to change the view when the page is in publish mode. That way we can show the same database in multiple views to multiple audiances and preserve the one source of truth principle that is the bases concepts of data bases. 
 

[Rachel Li]

Hi @Tami Dubi thanks for the feedback! To clarify the embedding experience - when embedding a database using its URL, the view used when the URL is copied is automatically set as default for your embed. If there is no view specified in the URL, the default view of the overall database (i.e. the one in the content tree) will be shown. 

At the moment, we're unable to support persisting displayed views for an embedded database based on user view selection or the ability to change the displayed view when the page is in publish mode, but will consider this feedback for the future. 

For now, you can set a new default view for an embed by copying the link to a view and replacing the existing smartlink URL with the new one. This view will then be shown whenever the page is viewed or edited, including after publishing a page.

If you want to change some view settings (i.e. filter, sort, hide fields, layout) without saving it to a new or existing view, you can use unsaved views for this. When you make changes to a view, a "Save view" dropdown will show up in the toolbar, and if you select "Copy link to current view" it'll generate a link to a view with all your current settings applied. You can then paste this as a smartlink and it'll show up as the default view for the smartlink.

We're aware that the existing default views experience may be confusing as other users have brought it up as well. We’re working on making this more clear in documentation and the UI!