Archive
#ProjectServer #PS2013 #Project Site permission sync clarification #SP2013 #SharePoint #ProjectOnline
   I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011. I am also a certified Prince2 Practitioner. This article has been cross posted from pwmather.wordpress.com (original article) |
Just a quick post to make you aware of a design change in the Project Server 2013 project site sync when in Project Server permission mode. The only issue is that you may find project team members without assignments are granted edit access to the associated project site rather than read access – this is now by design.
In Project Server 2010 if a user / resource was added to the project team but not assigned to any tasks they were added to the Readers (Microsoft Project Server) SharePoint group on the associated project site. This is different in Project Server 2013, when the users / resources are added to the project team but not assigned to tasks they are added to the Team Members (Project Web App Synchronized) SharePoint group rather than an equivalent Readers (Microsoft Project Web App) group. This is working as designed as there are now only two SharePoint groups on the Project Sites used in the permission sync:
Project Managers (Project Web App Synchronized)
Users who have published this project or who have Save Project permission in Microsoft Project Web App.
Team Members (Project Web App Synchronized)
Users who have assignments in this project in Microsoft Project Web App.
This could be misleading if you used 2010 and also if you view the SharePoint permission level descriptions. The Project Server 2013 Project Site permission levels can be seen below:
The “Readers (Microsoft Project Web App)” states “Users who have been added to this project in Microsoft Project Web App, but not assigned to tasks.”
Also the “Team Members (Project Web App Synchronized)” SharePoint group permission description is not quite accurate as it should states that it also includes project team members without assignments:
“Users who have assignments in this project in Microsoft Project Web App”
Hope that helps.
Am speaking at #SPSUK next week
Just a quick post since I forgot to mention that I will be speaking at SharePoint Saturday UK next week, this is the 9th November and in the middle of Leicestershire (I had to check on Google Maps myself again).
To make the session a bit more lively I will be presenting with my friend and Sharepoint Architect Ben Ahmed the latest in Business Intelligence and open data stream from Enterprise Systems such as CRM.
Anything that has “power” prefixed is on the menu: PowerQuery, PowerPivot, PowerView and even PowerMaps 3D). A very exciting subject to make boring data actually beautiful and interesting in just a few clicks !
SharePoint Saturday is usually a great day where subject-matters people sacrifice one family day to learn and socialise with others, this one is going to be really cool as we are now getting the benefits of months of real business stories of SharePoint 2013 and Office 365.
More info about the event here http://lanyrd.com/2013/spsuk.
via François on Sharepoint http://sharepointfrancois.wordpress.com/2013/11/02/am-speaking-at-spsuk-next-week/
 French native Sharepoint Consultant living in London. A crossway between a designer, developer and system architect. Prefers stretching the limit of out-of-the-box features rather than breaking them into code. When not working with Microsoft Sharepoint François is often found on Web2.0 News sites and related social networking tools.
This article has been cross posted from sharepointfrancois.wordpress.com/ (original article) |
Changing #SharePoint Central Admin Regional Settings stops the #PowerPivot Dashboard timer job #SP2013 #PS2013
|
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011. I am also a certified Prince2 Practitioner. This article has been cross posted from pwmather.wordpress.com (original article) |
Take care when updating the Central Admin regional settings as certain things stop working. The link to update the region settings doesn’t exist on the Site Settings menu probably for this reason but you can type the URL manually and access the page. Just add _layouts/15/regionalsetng.aspx to the URL.
Central Admin region settings were updated to English (United Kingdom), which is ID 2057.
An example of functionality that stops working is the PowerPivot Dashboard Processing Timer Job:
For the benefit of the search engines:
‘The Execute method of job definition Microsoft.AnalysisServices.SPAdding.UsageProcessingTimerJob(ID 5144359a-e86d-429f-8a5c-8c06cca109ee) threw an exception’
The following error is thrown in the URL logs:
For the benefit of the search engines:
Failed to load ‘http://sp13:15000/PowerPivot%20Management/567b4062-7a0b-4b24-a7f5-994bbed90cf1/2057/Server%20Health.xlsx’ with error: ‘The workbook does not exist at the specified location’
This error lead us to the fix. Notice the 2057 in the URL. Navigating the the PowerPivot Management library, there was no 2057 folder, only a 1033 folder.
A 2057 folder doesn’t exist, on 1033 – for English (United States):
At this point you can either create a a new folder for the correct locale in this case 2057 for English (United Kingdom), then copy the 3 documents shown below from the 1033 folder to the 2057 folder:
The timer job will now run successfully and the dashboard will update. The other option is to set the regional settings for Central Admin back to English (United States) – probably the recommended fix!
The the Dashboard will update and show data:
Don’t be fooled by InfoPath login prompt
A short sharing since I was amazed of the quality of feedback I received today from InfoPath and could have spent hours on this.
Steps:
- Create an infopath form (here 2013, but may be the same in previous versions as it hasn’t moved that much at all since 2007)
- Publish it to Sharepoint (2013) as a Content Type
- Bang ! Infopath prompts for a login/password for the Webs.asmx web service
- Entering any login still fails.
After a bit of thinking I went back a few step on that Publishing dialog box and noticed that I pasted some text that my client wanted to see displayed and it was just that: InfoPath didn’t like to transform the Description of the form or Sharepoint refused it because some characters were incorrectly formatted.
So don’t be fooled by InfoPath / Sharepoint, the error doesn’t always lays where you think it is.
via François on Sharepoint http://sharepointfrancois.wordpress.com/2013/10/18/dont-be-fooled-by-infopath-login-prompt/
|
French native Sharepoint Consultant living in London. A crossway between a designer, developer and system architect. Prefers stretching the limit of out-of-the-box features rather than breaking them into code. When not working with Microsoft Sharepoint François is often found on Web2.0 News sites and related social networking tools.
This article has been cross posted from sharepointfrancois.wordpress.com/ (original article) |
Take care when deleting the #Project Ideas list in #ProjectServer #PS2013 #SP2013 #SharePoint #ProjectOnline #PPM
|
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011. I am also a certified Prince2 Practitioner. This article has been cross posted from pwmather.wordpress.com (original article) |
Just a quick blog post to ensure you take care when deleting the project ideas list and to let you know of potential issues with deleting projects that were created via the deleted project ideas list.
This post covers the issues you will see when trying to delete a project from Project Server that was created from a project ideas list after the list was deleted.
Example Project Ideas list:
Project created in Project Server from the Project Ideas list above:
Delete the Project Ideas list from the “List Settings” > “Delete this list” option.
Now try to delete the project that was initiated from the Project Ideas list, in this example delete the PM Test Project from the Delete Enterprise Objects menu in server settings. Navigate to the Project Server queue and you will notice that Project Delete job fails:
The key error is:
Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.RemoveIdeaListLinkMessage‘ messageID=’8′ stage=” blocking=’Undefined’
You will see the the project still exists in the Project Center:
But trying to access the project details gives an error:
Checking the Delete Enterprise Objects page shows that the project is not visible when selecting “Delete draft and published projects”:
Change to “Delete only published projects” shows the project:
Attempting the delete again throws the same error.
My advice at this stage is to recover the deleted Project Ideas lists if possible. In this example I still had the Project Ideas list in the PWA site recycle bin. After restoring this deleted list, the subsequent delete job for the “PM Test Project” completed successfully.
With this in mind, I would recommend that you do not delete any PWA lists that have been used to create projects in Project Server.
Project Challenge 2013 #ProjectServer #PS2013 #SP2013 #projchallenge #pmot
|
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011. I am also a certified Prince2 Practitioner. This article has been cross posted from pwmather.wordpress.com (original article) |
Just a quick post to let you know that we (CPS) will have a stand at Project Challenge 2013. We will be on stand 72. CPS are also presenting, details below:
Wednesday 16 October 2013 – 14.00
Title: Portfolio management – how do I even get this on the executive agenda?
Speaker: David Dunning, Professional Services Director, CPS
http://www.projchallenge.com/case_studies_expertise.cfm
Tuesday 15 October 2013 – 11.30
Title: Microsoft Portfolio and Project Management made simple! Discover how effortless online and on-premise deployments are now a reality
Speaker: Ivan Lloyd, Product Lead, Corporate Project Solutions
Wednesday 16 October 2013 – 12.30
Title: Microsoft Portfolio and Project Management made simple! Discover how effortless online and on-premise deployments are now a reality
Speaker: Ivan Lloyd, Product Lead, Corporate Project Solutions
http://www.projchallenge.com/presentations.cfm
I will also be around at the exhibition on Wednesday – come and say hello 
#ProjectServer and #SharePoint 2010 / 2013 October 2013 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProject
|
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011. I am also a certified Prince2 Practitioner. This article has been cross posted from pwmather.wordpress.com (original article) |
The Office 2013 October 2013 Cumulative Updates are now available, please see the links below:
http://support.microsoft.com/kb/2887714
Project Server 2013 Server Roll up package October 2013 CU (Recommended):
***Delayed***
Project Server 2013 October 2013 CU (Included in the Server Roll up package):
http://support.microsoft.com/kb/2825659 & http://support.microsoft.com/kb/2760465
Project 2013 October 2013 CU:
http://support.microsoft.com/kb/2825651
Also worth noting, if you haven’t done so already, install the March 2013 Public update: http://support.microsoft.com/kb/2768001 if installing the October 2013 CU.
The Office 2010 October 2013 Cumulative Updates are now available, please see the links below:
http://support.microsoft.com/kb/2887713
Project Server 2010 Server Roll up package October 2013 CU (Recommended):
http://support.microsoft.com/kb/2825793
Project Server 2010 October 2013 CU (Included in the Server Roll up package):
http://support.microsoft.com/kb/2825816 & http://support.microsoft.com/kb/2825803
Project 2010 October 2013 CU:
http://support.microsoft.com/kb/2825812
Remember SP1 or SP2 is a pre-requisite for the Office 2010 October 2013 CUs.
As always, test these updates on a replica test environment before deploying to production.
Better logging in SharePoint
Just a very quick post so i can remember this post which describes 5 different approaches to custom logging within SharePoint.
http://spdevlab.com/2013/06/21/5-suggestions-to-implement-a-better-logging-in-sharepoint/
via Buzz Blog http://paulbuzzblog.wordpress.com/2013/10/01/better-logging-in-sharepoint/
 Paul is a an expert SharePoint and Project Server developer and is responsible for designing and implementing custom solutions on client systems using the latest SharePoint and .NET technologies.
Paul has extensive experience with SharePoint systems across all sizes of implementation, ranging from small to large farms and has an excellent understanding of all the elements of SharePoint. This article has been cross posted from paulbuzzblog.wordpress.com (original article) |
Recursive rules in InfoPath–How to prevent
A while ago I had a scenario in an InfoPath form where the user could either enter an amount or a percentage value. This value would then get added to a total already in the form. The requirement is that the user enters either value and the form then calculates the other one.
So if I enter a number then the percentage gets calculated. If I entered the percentage then the number value gets calculated.
So I quickly setup some rules so that when the value changed the percentage or the whole numbers gets calculated and updates the relevant field. This creates a loop of continually updated fields.
I had hoped that some clever InfoPath “stuff” would just make this work and I wouldn’t have to worry about the issue. This didn’t work and caused the form to fail or the fields would not update correctly.
The solution to this problem is that you need a third field to control the updates. Mine is called “Calculating” and is a simple Boolean field.
Now in the rules for Field1 (number) and Field2 (percentage) the first thing to do is to check that calculating = 0 then set calculating = 1 and then set your field. At the end set Calculating back to 0.
This is just a very simple implementation of a lock but it stops the InfoPath rules going crazy.
Pictures explain everything
via Buzz Blog http://paulbuzzblog.wordpress.com/2013/09/24/recursive-rules-in-infopathhow-to-prevent/
|
Paul is a an expert SharePoint and Project Server developer and is responsible for designing and implementing custom solutions on client systems using the latest SharePoint and .NET technologies.
Paul has extensive experience with SharePoint systems across all sizes of implementation, ranging from small to large farms and has an excellent understanding of all the elements of SharePoint. This article has been cross posted from paulbuzzblog.wordpress.com (original article) |
Programmatically Disable Event Firing on List Item Update in SharePoint 2010
All credit to the original post here
The short version for my future reference is
Create a simple class
public classEventFiring : SPItemEventReceiver { public void DisableHandleEventFiring() { this.EventFiringEnabled =false; } public void EnableHandleEventFiring() { this.EventFiringEnabled =true; } }
Then use this to disable events
using (SPWeb web = site.OpenWeb()) { SPList list = web.Lists.TryGetList("Custom"); SPListItem item = list.GetItemById(34); item["Title"] ="Updated Successfully"; EventFiring eventFiring = newEventFiring(); eventFiring.DisableHandleEventFiring(); item.Update(); eventFiring.EnableHandleEventFiring(); Console.WriteLine("Updated Successfully"); Console.ReadLine(); } }
via Buzz Blog http://paulbuzzblog.wordpress.com/2013/09/19/programmatically-disable-event-firing-on-list-item-update-in-sharepoint-2010/
|
Paul is a an expert SharePoint and Project Server developer and is responsible for designing and implementing custom solutions on client systems using the latest SharePoint and .NET technologies.
Paul has extensive experience with SharePoint systems across all sizes of implementation, ranging from small to large farms and has an excellent understanding of all the elements of SharePoint. This article has been cross posted from paulbuzzblog.wordpress.com (original article) |
SharePoint (and Project Server) Shenanigans 
You must be logged in to post a comment.