how to insert project drilldown web part in to project workspace

[Vaso Vukovic]

Is there a way to insert a link/web part project drillown (the one you'd
normally get under Project Center view (
...../PWA/ProjectDrillDown.aspx?_projectUID=<Project UID value here>) in to
the project workspace when it is provisioned, or to make it a part of the
provisioning template?

I could add a link manually to the quicklaunch area but I'm looking to
automate the process. Any hints??

 

[Vaso Vukovic]

Thanks Johnathan,

I am already doing all the steps related to creating the template,
registering and provisioning. Note that we use top level site 'a' to host PWA
and top level site 'b' (different URL, web sites etc) to host project
workspaces. It could be that I have not deployed/activated some web part on
the site 'b'. What is the name of the solution/web part that I should be
looking for?? I can't see 'Project Detilas' web part listed when editing a
sample (or new) web page.

 

[Vaso Vukovic]

Ok, this is what I've found so far..

Because workspaces and pwa are hosted on different sited, the required web
parts need to be exported, PSI url parameter set (xml edit), then imported in
to the site collection that is hosting workspaces...
So I did that for 'My timesheet' and 'Project Details' webparts. Now I can
import them on to the workspace. BUT, once there, how do you get the user to
select which project details they want to see?? When in edit mode, I can
select project name from the dropdown list, but as soon as I exit page edit
mode then the web part loses that information and gives me just :

"Project Center cannot access the project(s) you are trying to view. It is
most likely that you either don't have permissions to view the project,
another user has deleted this project(s) before you were able to view it or
that another user is in the process of publishing the project."
...but access is not a problem as I am collection admin on all sites and
member of Project Server admin under PWA...

Any ideas how to move on from here.. ?

 

[Jonathan Sofer [MVP]]

So are you using the project workspaces that are automatically provisioned
by Project Server on the initial project publish? What settings do you have
in PWA>Server Settings>Project Workspace Provisioning Settings? And do you
see the project workspaces you are using linked to the projects when going
to PWA>Server Settings>Project Workspaces?

It sounds like you might be trying to use a workspace site that is not
linked to the project under PWA>Server Settings>Project Workspace in which
case the workspace does not know what the Project UID is.

Jonathan

 

[Vaso Vukovic]

Q1. So are you using the project workspaces that are automatically
provisioned by Project Server on the initial project publish?
A1. Yes

Q2.What settings do you have in PWA>Server Settings>Project Workspace
Provisioning Settings?

A2: Site URL:
- Default web app: http://projects.domain.com
- Site URL: pws (this is my collection hosting the workspaces)
- Default Language is English
- Default Project Workspace template is selected (actual name is not
relevant)
- Provisioning is set to 'Allow users to manually create project
workspaces in Project Server' (but this is limited otherwise by special
security group)
- "heck to automatically synchronize Project Web Access users with
Project Workspaces when they are created" is CHECKED..

Q3: And do you see the project workspaces you are using linked to the
projects when going to PWA>Server Settings>Project Workspaces?

A3: Yes..

I am collection admin on all PWA and Workspace collection rtoot sites.

Now, I did a bit of readinf since this was posted and found out that if you
insert 'My timesheet' webpart it works fine.. same for my tasks. the only
ones that do NOT work are the project center web parts (details and
drilldown). Quite a few poepl seem to have the same results and one of the
workarounds was to insert timesheet web part at top of the page, hide it and
insert the drildown under it but visible. then it worked for many but not for
me and few others.. I am not sure what is the difference but thats where I am
up to now.

Tanks,
Vaso

 

[Matt Stevenson (UK)]

Hi Vaso,

I have this same scenario on my current contract.
We started with the a new workspace created under the root PWA site
We put the Project Details webpart on the home page of each workspace.
(as this point we also get the message you get above)
We saved the new site as a template in sharepoint (as normal).
Exported it (.stp file)
Then registered this template into Sharepoint. (using STSADM.EXE)
Then set this new template as the default of each workspace. (server settings)

We have all workspaces in the same site collection under
http://projectserver/pwa/... (which is different to you)
But after publishing a new project and creating a new site with this
template, opening the workspace displays the project details view of the
associated plan automatically.

FYI: if I look at the site using the server it also displays the error
message you got, but this is because we have not got the PWA ActiveX controls
installed on the server.

Don't know if this info helps you.

Our frustration is that when we give all users read-only access to a
project's workspace (adding NT Authority\Authenticated Users as Reader) then
these users get an error on opening the home page "An Unexpected Error has
Occured" because they don't have the associated PS2007 user account!

Ideally we'd restrict when the Project Details webpart is displayed by using
the Target Audiences field in the Webpart properties, but this only allows
group names and of course PS2007 synch's users into the workspace by
individual name rather than putting them into a group. Pook!

If you know a way round this one, please let me know.

best wishes

MLCS