Two projects linked to the same sharepoint site

[Jim]

Anyone know of any issues with pointing more than one project to the same
Sharepoint site? I noticed that, through the Manage Sharepoint Windows
services area of the web tools that you can edit the sharepoint link for a
project. We have a situation that could be solved by pointing 2 projects to
the same site. Let me know if anyone has done this and what
complications/issues/features you encountered.

Thanks,

Jim

 

[Gary L. Chefetz \(MVP\)]

Jim:

The interface tool will not allow this to happen in that page. It will throw
an error. Plus, if you use anything other than the what Project Server
expects the URL to be for the SharePoint site, links from the Documents,
Issues and Risks sections in PWA will not work. This actually represents a
feature degradation from 2002, and I can assure you that the product teams
has heard complaints about it.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project

-

 

[Jim]

Gary,

Thanks for the info. You can however remove the link from Project A and
then change the link for Project B to it. However, based on your message,
doing this will negate the ability to link issues to tasks, have issues show
up in the resources list, etc.

Thanks for your help. Definitely not what I wanted to hear.

Jim

 

[Jim]

UPDATE!

Gary,

I am not finding this to be the case. We have a yearly maintenance project.
The 2004 was closed and the 2005 created. There were outstanding issues,
documents, etc. on the site for the old project that we wanted in the new
site. Rather than migrate, we removed the link from the old project and
changed the link of the new one to the old site. Everything appears to be
working perfectly. I created a test issue, assigned it to myself and linked
it to a task on the project. I double checked that the project/tasks that it
listed to link, were the new project and not the old. The issue shows up in
my issues list and the links are working correctly.

I wonder that since both sites were created by Project that the
functionality will work properly when changing the link.

Let me know if you want more detail.

Jim

 

[Gary L. Chefetz \(MVP\)]

Jim:

If you delete one, you can add the URL to a new site. I read your subject
line to mean "two pointing to the same site at the same time." The
integration construct demands monogamous relationships between Projects and
their SharePoint sites. Serial monogamy is OK.

To some extent, you can work around the limitations of the PWA interface by
poking around in the database. I don't advise this unless you know what
you're doing.


--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project

-

 

[Jim]

Understood and I agree. We have been trying to find a way to handle this
year to year maintenance plan issue. So far this works the best. If this
hadn't come up, we were looking at copying the issues from one datasheet view
to the other datasheet view, but that has the drawback of changing the issue
numbers, create_date, created_by, etc. Those fields cannot be copied and
pasted.

It worked OK though. The issues and all the information moved over.
Definitely not an ideal solution though. The one positive solution that came
out of it though, was it provided us a template Excel structure for importing
issues. We have had several outside files (Excel, Word, etc) containing
issues that needed to be added to the issues. Originally we were rekeying,
now we put them into a spreadsheet, reformat the information to fit the
columns in the Datasheet view and copy and paste. Works great.

Thanks for all your help.

Jim