|
Background:
We often get requests
to limit list items to a section of people like HR, IT, PMO, etc. HR should see
fewer items that other groups should not and vice versa. The solution for this
problem appears straight forward (by breaking permissions of items and assigning
them to corresponding SPGroups). However, this approach leads to serious
performance issues for a large number of items and can bring entire SPFarm
down!
Why?
The recommended number
of unique security scopes for a SPList is 5000. When the number of unique
security scopes for a list exceeds the value of the list view threshold (set by
default at 5,000 list items), additional SQL Server round trips take place when
the list is viewed, and this can adversely affect list view
performance.
Resolution
Possible workaround for
this problem is to have folder level security in SPList. For the above problem
statement, we will be having folders for HR, IT, PMO in SPList and HR folder
will be accessed only by HR and Admin SPGroups (same approach for other folders
as well)
With this change, all
items under HR folder will inherit permissions from HR folder instead of having
separate permissions. Below is the comparison between item level permissions and
folder level permissions
List Item
Count:
2000
Without using
Folders –We would be
having more than 2000 unique security scopes
With using
Folder – We would be having 4 unique security scopes
(Permissions for List itself and Permissions for 3 folders)
|
Thursday, October 31, 2013
Folder-Level Permissions in SharePoint List
Partial Page Exclusion in SharePoint Search
Background:
Out of the
box search results in SharePoint shows unnecessary data such as navigation, left
nav, footer, right nav etc., that may not be useful to end user. Fortunately,
it’s easy to exclude those items from appearing in search results by using a
technique called “Partial Page Exclusion”.
How to use:
Just include
a class called “noindex” for the items that needs to be excluded from search
results. This tells the crawler to ignore those items. Here is a sample example
in which crawler is forced to crawl only content present in body class. All
other items are ignored.
<!DOCTYPE
html>
<head>
<meta
charset="utf-8"
/>
<title></title>
</head>
<body>
<div
class="wrapper">
<div
class="header
noindex">
// Header Data
</div>
<div
class="topnav
noindex">
// Navigation
</div>
<div
class="body">
// Header Data
</div>
<div
class="footer
noindex">
// Footer Data
</div>
</div>
</body>
</html>
Wednesday, September 25, 2013
Error Publishing Content Type: No valid proxy can be found to do this operation
Hi All,
Below is the error we faced when trying to publish a content type from content type hub:
"No valid proxy can be found to do this operation"
Resolution:
Make sure that on content type hub (source), Content Type Syndication Hub site collection feature is activated.
Thanks :)
Below is the error we faced when trying to publish a content type from content type hub:
"No valid proxy can be found to do this operation"
Resolution:
Make sure that on content type hub (source), Content Type Syndication Hub site collection feature is activated.
Thanks :)
Subscribe to:
Posts (Atom)