I used my 1-on-1 call with my boss to finally give him some time to give permission to the rest of our team access to restricted pages that I created for our team only. I had originally was able to view and edit the page just fine. After our meeting, I realized that I no longer had access to the page. I checked with my coworker, and he now had access.
This was bizarre. Of course, I let me boss know. He tried a couple things. None of them worked. When we finally gave up messaging back and forth, he shared his desktop. I then saw that I was in the list, as I was before. Then we realized that I lost the restrictions when we added the others.
I did not want to waste any more of my boss' time so, I speculate that we had access before because there were no other restricted users. Once the restricted users were added, we lost access to the view rights. I am assuming that I still had edit rights. In theory, I could test this by keeping a link to the edit page of the restricted page.
In conclusion, users with edit rights has view rights automatically if there are no restricted viewing rights. Users with edit rights lose the viewing rights once there are other users with viewing rights. Thus users with edit rights has to also be added to the viewing rights list.
Food for thought, are there any cases where I would ever need edit rights but not viewing rights? I would still see the content when editing the page.
Thursday, May 29, 2014
Review: SharePoint 2010 for Dummies by Vanessa L. Williams
I have just started to really sit-down and learn SharePoint Designer for the past week. Prior to this, I have just been an end-user. Unfortunately, a project has been transitioned to me which requires me to configure SharePoint. I have bought the SharePoint 2010 for Dummies by Vanessa L. Williams. So far, the book does a great job in getting me started.
For the purposes of my project, I think there were a lot more advanced 'techniques' that are not covered in the book. Google has been sufficient in those areas. Most of the time, I learn that SharePoint cannot even do whatever I need. There is also a section for forms that require InfoPath which I do not have access to, so I do not have much to comment on that part. I also do not have enterprise, so the last sections are rather useless to me.
Overall, this is a good introduction book. I was able to grasp a lot of the SharePoint terms that made it much easier to search on Google. The way they designed the architecture of SharePoint is not very intuitive for a developer. It may actually be a bit more intuitive for a non-developer, because I spent a lot of time trying to figure how to join lists and figuring the limitations to web-parts.
I should also add that this book is more useful for those who only have access to the Designer. If you are looking for a SharePoint server reference, this is not the book. There is another For Dummies series that cover that, "SharePoint 2010 All-in-One For Dummies". At least this is what appeared to be more server-related when I skimmed through it at Barnes & Nobles. I think it had both coding and admin maintenance, but more on the latter. The all-in-one version does not help at all with the Designer.
For the purposes of my project, I think there were a lot more advanced 'techniques' that are not covered in the book. Google has been sufficient in those areas. Most of the time, I learn that SharePoint cannot even do whatever I need. There is also a section for forms that require InfoPath which I do not have access to, so I do not have much to comment on that part. I also do not have enterprise, so the last sections are rather useless to me.
Overall, this is a good introduction book. I was able to grasp a lot of the SharePoint terms that made it much easier to search on Google. The way they designed the architecture of SharePoint is not very intuitive for a developer. It may actually be a bit more intuitive for a non-developer, because I spent a lot of time trying to figure how to join lists and figuring the limitations to web-parts.
I should also add that this book is more useful for those who only have access to the Designer. If you are looking for a SharePoint server reference, this is not the book. There is another For Dummies series that cover that, "SharePoint 2010 All-in-One For Dummies". At least this is what appeared to be more server-related when I skimmed through it at Barnes & Nobles. I think it had both coding and admin maintenance, but more on the latter. The all-in-one version does not help at all with the Designer.
Work Life: SharePoint 2010 - Creating Workflow Error
The list of workflow actions on the server references an assembly that does not exist. Some actions will not be available. The assembly strong name is Microsoft.Office.Workflow.Actions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Contact your server administrator for more information.For me, I had to restart my SharePoint Designer which fixed the problem. My guess is because I opened it yesterday and left it open overnight. My VPN disconnected as usual when my machine goes to sleep-mode.
Here's another site that looked promising, but appears to require access to the server:
http://sharepoint.stackexchange.com/questions/68769/sharepoint-2010-sharepoint-designer-notification-the-list-of-workflow-actions
Subscribe to:
Posts (Atom)