Want to disable #Lync / #Skype #IM presence in #MSProject 2013?

April 15, 2015 at 9:26 am | Posted in Add-on, Administration, Configuration, Customisation, Functionality, Information | Leave a comment
Tags: , , , , , ,

If you want want to disable the Lync / Skype for Business presence in Project 2013, see the steps below.

Lync / Skype for Business Presence enabled:

image

Lync / Skype for Business Presence disabled:

 image

To do this, install the April 2015 Cumulative update for Project 2013 (fully test on a test machine before using in production): https://support.microsoft.com/en-us/kb/2965279

Then create the registry key as detailed in the KB article.

You can either do this manually or via PowerShell, an example PowerShell command can be seen below:

image

This will create the following key:

image

Always back up the registry before making any changes (manually or via PowerShell etc.)

To enable Lync / IM presence again update the DisableIMStatus key value data to 0 and restart Project.

Advertisements

#ProjectServer and #SharePoint 2010 / 2013 April 2015 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProject

April 15, 2015 at 7:56 am | Posted in Administration, CU, Fixes, Functionality, Information | Leave a comment
Tags: , , , , , , ,

The Office 2013 April 2015 Cumulative Updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/3050766

Project Server 2013 April 2015 Server Roll up package:
https://support.microsoft.com/en-us/kb/2965263

Project Server 2013 April 2015 CU:
https://support.microsoft.com/en-us/kb/2965278

Project 2013 April 2015 CU:
https://support.microsoft.com/en-us/kb/2965279

Also worth noting, if you haven’t done so already, install Service Pack 1 http://support2.microsoft.com/kb/2880556 first if installing the April 2015 CU.

The Office 2010 April 2015 Cumulative Updates are now available, please see the links below:

https://support.microsoft.com/en-us/kb/3050766

Project Server 2010 April 2015 Server Roll up package:
https://support.microsoft.com/en-us/kb/2965293

Project Server 2010 April 2015 CU:
https://support.microsoft.com/en-us/kb/2965302

Project 2010 April 2015 CU:
https://support.microsoft.com/en-us/kb/2965204

SP2 is a pre-requisite for the Office 2010 April 2015 CUs.

As always, fully test these updates on a replica test environment before deploying to production.

#ProjectOnline / #ProjectServer reporting on auto / manually scheduled tasks #BI #Office365 #Excel #PowerQuery #PS2013

April 13, 2015 at 9:49 am | Posted in Add-on, Administration, Configuration, Functionality, Information, Reporting, Workarounds | 1 Comment
Tags: , , , , , , ,

One issue or query that has been raised a few times is that when reporting on manually scheduled tasks and auto scheduled tasks the Start / Finish date fields do not show the same data that they do in Project or PWA for the manually scheduled tasks. For example, take a look at the example project plan below:

image

If I generate a reporting for this project using the equivalent fields from the OData API, see below:

image

As you can see all tasks have start and finish dates. The Manually scheduled tasks that are either blank or have text displayed in Project Pro contain dates in the report. These default to the Project Start date. The OData query used is below:

Tasks()?$Select=ProjectName,TaskName,TaskStartDate,TaskFinishDate,TaskIndex

This can be quite misleading from a reporting point of view. There are two options (probably more but two documented here!), these are detailed below in order of preference:

Option 1:

The preferred option would be to create a calculated field in the report, in this example, as I am using Excel I will create this in Power Query. I have my dataset in the Power Query Editor like below:

image

The OData query used is below:

Tasks()?$Select=ProjectName,TaskName,TaskStartDate,TaskStartDateString,TaskFinishDate,TaskFinishDateString,TaskIsManuallyScheduled,TaskIndex

Now click Add Column > Add Custom Column:

image

Give the column a name then create the formula:

image

Click OK to add the new custom column, repeat for the finish date:

image

After re-ordering and removing some columns my dataset now looks like this in the Query Editor:

image

The final change is to update the Data Types of the columns, in this example I updated the TaskStartDate and TaskFinishDate columns to Date/Time and my calculated DisplayedStartDate and DisplayedFinishDate columns to Text:

image

Now I am happy with the query I click the Close & Load button on the Home tab:

image

This will load my data into Excel:

image

As you can see the data displayed in my calculated columns on my report match the data in the fields on my Project Plan:

image

Option 2:

The other option is to create new Enterprise Custom Fields in Project Online that are calculated. Using Start date as an example, create a task level text field that is based on  formula, the formula would be =[Start]. I have called the field “DisplayedStartDate”. In Project Pro:

image

In my updated Excel Report:

image

The OData query used is below:

Tasks()?$Select=ProjectName,TaskName,TaskStartDate,TaskFinishDate,DisplayedStartDate,TaskIndex

As you can see this also gives the correct data but does introduce two additional calculated task level fields in your Project Online configuration. It is recommended to keep the task level calculated fields to a minimum – ideally below 5 for performance reasons hence this option being the least preferred. 

#Project #MVP Award #ProjectOnline #PS2013 #ProjectServer #MVPBuzz #Microsoft

April 1, 2015 at 5:47 pm | Posted in Information, Personal | Leave a comment
Tags: , , ,

Some good news, I’m very pleased to announce that my Project MVP award was renewed for the third time after first being awarded in April 2013. I am really grateful for the recognition, especially as I still enjoy helping out the Project and Project Server / Project Online community so much. It is kind of a hobby of mine I guess, or maybe just an obsession!

Create a free website or blog at WordPress.com.
Entries and comments feeds.