Quantcast
Channel: Microsoft Online: SharePoint Online forum
Viewing all articles
Browse latest Browse all 10096

Sharepoint online document library views

$
0
0

I have a Diaconate formation program within my diocese. We are using a document library to host files associated with the candidates. Each candidate gets 3 views of the document library: Their files, the candidate files the board can access and the candidate files the formators can access.

I recently spent some time figuring out why quick edit was disabled for this library. It is because when I created the views, I set up the view style to be basic table. I should have left it set to default. Now I have to task of adjusting the setting for all 102 views. At least I have learned to leave things set to the default unless there is a compelling reason to switch. Anyways…

When I switched the style to default, I am able to use quick edit, but there is a problem. The toolbar at the top of the webpart which has new, upload, sync, and search options, also contains a view selector. How do I get rid of the view selector? In this context the view selector is confusing since users select a candidate before selecting the group and seeing the appropriate view for that candidate’s files. Being able to choose other views at that point is not what I want.

I did manage to find the CSS style of the item and set display:none as below:

.ms-pivotControl-container {                display:none;     }

I want to know if this will cause any issues elsewhere on the site as the item will no longer display because I added the CSS to the alternative CSS file. I didn't want to add an HTML Forms webpart in order to add the CSS to each view. That would take forever.

I hope i am not breaking site functionality. The reverse question is when I need the pivot control on a page, i could add CSS display to the page, but what type of display should I use?


Viewing all articles
Browse latest Browse all 10096

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>