View Multiple Published Projects At The Same Time

[mshohman]

I need an intergrated view of the Published Versions of several
projects. Using Project Server 2007 and Project Pro 2007.

I need the integrated view in Project Professional (PWA View is not
good enough to meet our needs for this view)

When creating a new Master Project, I can only insert projects from
the Working Data.

When opening a 'published' Master Project of projects on the server,
it always opens the Working Database version.

When opening an 'unpublished' Master Project of projects on the
server, it always opens the Working Database version.

Can anyone help? Thanks!!

I believe, when insert a Project into a Project, Project Professional
should allow the user to select Projects from the Published Database,
but I cannot, at least in my version....

Thanks,

Mike

 

[Rod Gill]

Project Professional 2007 always uses data from the working db. The
published db is a version configured for use in the web PWA tool, never for
Project pro. After a publish, the two sets of data should be the same.

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com

 

[mshohman]

Well, Project Professional doesn't always use data from the Working
DB. I can easily open the Published Version of a Project using Project
Professional 2007. Just click the Store = Published Radio Button in
the Open Project Dialog.

And if this is so, when I insert a Project into a master project, I
should be able to select Store = Published as well in the Insert
Project Dialog. But alas, I cannot. Aside from the 'Link to Project'
check box, the two dialogs are identical, so to speak.

I don't believe there is any legitmate technical reason why the above
feature cannot be supported, particuarly since PWA does exactly that.

And I appreciate that I can publish the Master Project and then use
PWA to achieve an integrated view of the Published Versions of
multiple projects. However, PWA lacks the full feature set of MS
Project Professional that my users require to produce PDF Reports of
the Integrated Schedules.

Thanks for you input, i appreciate it. Will start building custom
views in PWA, but its just not the same.....

 

[Rod Gill]

Hi,

To publish a project you must first save it, so the published version is no
more up to date, but can be out of date.

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com



Well, Project Professional doesn't always use data from the Working
DB. I can easily open the Published Version of a Project using Project
Professional 2007. Just click the Store = Published Radio Button in
the Open Project Dialog.

And if this is so, when I insert a Project into a master project, I
should be able to select Store = Published as well in the Insert
Project Dialog. But alas, I cannot. Aside from the 'Link to Project'
check box, the two dialogs are identical, so to speak.

I don't believe there is any legitmate technical reason why the above
feature cannot be supported, particuarly since PWA does exactly that.

And I appreciate that I can publish the Master Project and then use
PWA to achieve an integrated view of the Published Versions of
multiple projects. However, PWA lacks the full feature set of MS
Project Professional that my users require to produce PDF Reports of
the Integrated Schedules.

Thanks for you input, i appreciate it. Will start building custom
views in PWA, but its just not the same.....

 

[mshohman]

Sounds like you are challenging our need for an integrated view of
Published Data?? Strange...

The Published Version holds the official, public (in other words,
'Published') version of our Projects, open to all to view.

The Working Database holds the Working Version, where our Planners
enter prosposed updates, do scenario planning, and otherwise prepare
the schedules before publication. In our oganization, the Working
Database is the sandbox where our planners perform their jobs and get
everything optimized before official publication.

Once published, the entire organization needs access to the schedules,
and many of our users want to use Pro for this, many are not satisfied
with PWA, and most simply want PDF's prepared by our planners. Hence
the need for Published Data in Pro...

I do appreciate the help, cheers, Mike