PSI: Publish selected tasks only

S

Stephan Steiner

Hi

Does anybody know how the QueuePublish method in the Project
webservice works with regards to what is being published? E.g. if I
add say 4 new lines to the project which have no influence of the rest
of the project (except that the project duration might change.. but
there's no relation to previously existing tasks) and do a
QueuePublish, is it supposed to only publish the 4 lines I added, or
will everything be published (like it is by default in Project Server
2003)? If it's the latter, is there a way using PSI to ensure that
only the new tasks get published (publishing, at least with our 2003
solution, tends to overwrite certain information erroneously.. e.g. it
brings back tasks that have been hidden in the timesheet - so we
currently have to jump through some hoops to automatically only
publish the lines we want).

Regards
Stephan
 
S

Stephen Sanderlin

A publish operates on the entire project. You cannot override this. If
you need to hide tasks, use the "Publish" field on the task or set the
resource's assignment booking type to Proposed from Committed. I believe
the bug that would display assignments for Proposed resources was fixed
in SP1.



This is the downside of the changes Microsoft made in the publishing
facility between 2003 and 2007, but I think it's far outweighed by the
benefits the simplification offers.

--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com
 
S

Stephan Steiner

Stephen

Thanks for the info. This approach isn't so different from what we're
doing today.. we have our own Publish EF and use PIA to load the
project in the Project Client, save, then select a view that shows
only tasks with that EF set to true and publish all visible tasks. So
for me it's still a big step forward.. I hated having to automated the
Project Client (I don't trust it at all.. we've had projects that
would block the client, and we have tasks that that client re-opens
(makes visible again and bumps up remaining work from 0) every time
after approval and MS is unable to fix the problem) and I'm surprised
that it has worked almost without major meltdowns but I feel much more
confident when I'm using the same APIs as every other application
accessing the data store.

I take it that the Publish field is by default set to true, is that
correct? And will it revert to true upon re-opening the project or
will it stay on false unless changed again?

Regards
Stephan
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

PS2007: Add a new task between two existing tasks Part 2 2
Failure submitting task updates using PSI 3
Splits in Project Server 2007 PSI 1
PSI external tasks 0
Get only a subset of tasks, using Project Server 2007 PSI 1
Updated Custom Field by PSI Not Showing in Project Professional 2
How to get TASK_ID field for summary tasks without using Project.a 2
Project Online Timesheets Actuals Mismatches - data not publishing to projects 0

Top