Impacts of setting the publish task to "No" Project Server 2007

[frankod]

Hi All,

We are setting the publish task field to "No" in MS Project for selected
tasks that we don't want displayed in users timesheets. However it would
appear that values associated with these unpublished tasks are then not
available for reporting on from the OLAP cube (makes sense I suppose) and, at
least in some cases, from the resource centre when reviewing historical
actual work values.

Can someone pls advise what are the reporting consequences of setting the
publish task field to No, in terms of actual values, baseline values etc or
point me at a document/blog that describes this. Many thanks.

 

[Jonathan Sofer [MVP]]

I believe that setting the project published field to "No" would remove all
data related to that task from the Published database and therefore from the
Reporting database and the OLAP cubes.

If you are setting the Published filed to "No" on tasks because your
intention is to hide the assignments from the resources "My Tasks" page but
you do not want the data to be removed from the Published, Reporting and
OLAP cubes then maybe another alternative to create user account in the
Enterprise Resource Pool called "Remove Assignments Account" (you will have
to have a windows account associated to it) and then add this account to the
Resource Sheet via Build Team and then set it as the "Assignment Owner" for
the particular tasks you want to remove the the resource's My Tasks page.

Jonathan

 

[frankod]

Thanks Jonathan,
That's what I was expecting as well but I believe if the task was previously
published and then set to not publish the originally published values are
retained. I will need to test this further but think this is the case based