Unfortunately it is not backward compatible, and the below is the error message when trying Open Site for a Microsoft SharePoint 2007 site:
Showing posts with label Microsoft SharePoint Administration. Show all posts
Showing posts with label Microsoft SharePoint Administration. Show all posts
Monday, 29 December 2014
Sunday, 28 December 2014
Adding multiple group owners for SharePoint 2010 site
When you edit the Group Settings for a SharePoint group, and try to add multiple owners so that they can all edit the membership for this group; you got the message:
You are only allowed to enter one item.
You are only allowed to enter one item.
The workaround for that is to define the group owner as another SharePoint group rather than multiple users.
Thursday, 25 December 2014
SharePoint 2010 Custom List: Row Level Secuity
Business Case: Sharing a comprehensive list data among different stakeholders where every stakeholder can view\read only those row as per her Role\Unit
Resolution:
(1) Export the existing list data into SharePoint custom list including the column: Unit.
(2) Add a new empty temporary column: trigger update.
(3) Build a row level security based on the field row for each row.
Let's elaborate on step number (3), where we are going to create a new workflow assocuated with this list and to run on every Create\Update item.
a) Create Permissions groups within SharePoint.
Each Group will be equivalent to each Unit, same name.
b) Create the workflow:
1) Open the SharePoint site with Microsoft SharePoint Designer.
2) Navigation --> Site Objects --> Lists and Libraries --> Open that specific custom list with the data.
3) From the upper toolbar: list Workflow to create a list workflow.
.png)
4) Set Start options for the workflow: Item Created\Changed.
5) Edit Workflow.
6) Click Impersonation Step on the top toolbar to add a new Impersonation step, then remove the existing Step 1.
7) Click on the orange underline to activate the toolbar Action button.
8) Add a new action: Replace List Item Permissions.
9) Similarly, beneath it, add a new action: Add List Item Permissions.
10) Since we are interested to set the security on the item level, this workflow will do the function on the current item, replace this list in both steps with Current Item
11) To guarantee that the owners still have the permissions to access this list item, grant site owners all the permissions in the first replace step.
12) Now, to the core idea which is matching the field Unit with the equivalent group.
The result is that each row will have Read Access granted to the group members for the equivalent members of the group with the same name.
13) Save and Publish.
14) It is recommended to break the inheritance for this custom list so that the list items would be immune to any permissions changes at higher levels.
15) One time step: activate the workflow on all the items through through filling in the temporary column created earlier: Trigger Update. A simple way to do it is through filling it within the Spreadsheet view for the list. Delete the temporary column:Trigger Update from the list.
Resolution:
(1) Export the existing list data into SharePoint custom list including the column: Unit.
(2) Add a new empty temporary column: trigger update.
(3) Build a row level security based on the field row for each row.
Let's elaborate on step number (3), where we are going to create a new workflow assocuated with this list and to run on every Create\Update item.
a) Create Permissions groups within SharePoint.
Each Group will be equivalent to each Unit, same name.
b) Create the workflow:
1) Open the SharePoint site with Microsoft SharePoint Designer.
2) Navigation --> Site Objects --> Lists and Libraries --> Open that specific custom list with the data.
3) From the upper toolbar: list Workflow to create a list workflow.
4) Set Start options for the workflow: Item Created\Changed.
6) Click Impersonation Step on the top toolbar to add a new Impersonation step, then remove the existing Step 1.
7) Click on the orange underline to activate the toolbar Action button.
8) Add a new action: Replace List Item Permissions.
9) Similarly, beneath it, add a new action: Add List Item Permissions.
10) Since we are interested to set the security on the item level, this workflow will do the function on the current item, replace this list in both steps with Current Item
11) To guarantee that the owners still have the permissions to access this list item, grant site owners all the permissions in the first replace step.
12) Now, to the core idea which is matching the field Unit with the equivalent group.
The result is that each row will have Read Access granted to the group members for the equivalent members of the group with the same name.
13) Save and Publish.
14) It is recommended to break the inheritance for this custom list so that the list items would be immune to any permissions changes at higher levels.
15) One time step: activate the workflow on all the items through through filling in the temporary column created earlier: Trigger Update. A simple way to do it is through filling it within the Spreadsheet view for the list. Delete the temporary column:Trigger Update from the list.
Sunday, 30 November 2014
Problem: Internet Explorer 11 keeps loading Sharepoint 2010 toolbar forever; Loading....
Problem:
Proposed solution:
1) Command prompt or Run command: gpedit.msc
2) Enable Allow
3) Command prompt or Run command: ipconfig /flushdns
Thanks a lot Wilson for sharing this solution, actually my reference for this blog post!
http://sharepointegg.blogspot.com/2011/06/sharepoint-2010-ribbon-stuck-at-loading.html
Wednesday, 22 January 2014
SharePoint 2010: Managing user alerts
Site Actions
--> Site Settings
--> Site Administration
--> User alerts
--> Site Settings
--> Site Administration
--> User alerts
Thursday, 29 August 2013
Security Tip: SharePoint 2010 Access to all users (Authenticated users)
Site Actions -->
Site Permissions -->
Grant Permissions -->
Select Users --> NT AUTHORITY\authenticated users
What happened to Add All Authenticated Users?
Site Permissions -->
Grant Permissions -->
Select Users --> NT AUTHORITY\authenticated users
What happened to Add All Authenticated Users?
Sunday, 26 August 2012
Difference between SharePoint "View Only" & Read permissions
View Only: Can view all site objects within the application; however, unable to open content within client side applications.
Quote:
"If the document has a server-side file handler available, they can only view the document using the server-side file handler."
UnQuote
Read: View Only + open content within client side applications, such as word documents from Ms Office Word application on the client.
Quote:
"If the document has a server-side file handler available, they can only view the document using the server-side file handler."
UnQuote
Read: View Only + open content within client side applications, such as word documents from Ms Office Word application on the client.
Subscribe to:
Posts (Atom)