B
Brian Lukanic
I make use of the Project Workspace for our team resources to use that as
their collaboration area almost as much as the PWA pages. On that Workspace,
I want a standard set of fields to display the key attributes of the project,
such as: Estimated golive date, The link to the contract on our document
server (not Sharepoint,) a revenue field (how much we are getting paid for
the project,) and legal name of the project (The SOW name.) Perhaps also a
field stating whether the project is an internal iniative or a client-facing
saold project.
The end result is this: I'm picturing some type of web part on the workspace
that displays these fields in a standard way for every project on every
workspace. I also want/am willing to have my PMs manually enter this
information once (except for golive data, which might change) at the onset of
a project. So I don't need this automated or anything, although it would be
GREAT to be able to display the project end date (estimated golive date)
dynamically as it changes during the life of the project.
I also would like the ability to report off these fields eventually - either
by the native reporting services in Project Server or by direct querying.
So my question is: What's the best way to get this data into the system? I
can think of two options. Option 1: Ask the PM to manually enter the
attribute information into the custom Sharepoint list that will be the
display of that information. Seems like an acceptable option, but seems
low-tech compared to option 2. Option 2: Create a custom enterprise field on
Server for each attribute and make them be required by the PM upon initial
publishing. I am ok with the PM getting up to 6 required fields as hoops to
go through before publishing. Then, the Sharepoint web part that displays
this key information would be some flavor of a Project Details web part that
is a custom view created to show only the 6 enterprise fields and perhaps the
project end date from line 0 which WOULD be able to dynamically update since
it is driven off the PM's republished schedule. I would then keep the display
depth of the web part to be very shallow, since there'd be only one header
row and one data row for all of this information.
Can somebody validate my thinking and/or recommend an alternate strategy?
their collaboration area almost as much as the PWA pages. On that Workspace,
I want a standard set of fields to display the key attributes of the project,
such as: Estimated golive date, The link to the contract on our document
server (not Sharepoint,) a revenue field (how much we are getting paid for
the project,) and legal name of the project (The SOW name.) Perhaps also a
field stating whether the project is an internal iniative or a client-facing
saold project.
The end result is this: I'm picturing some type of web part on the workspace
that displays these fields in a standard way for every project on every
workspace. I also want/am willing to have my PMs manually enter this
information once (except for golive data, which might change) at the onset of
a project. So I don't need this automated or anything, although it would be
GREAT to be able to display the project end date (estimated golive date)
dynamically as it changes during the life of the project.
I also would like the ability to report off these fields eventually - either
by the native reporting services in Project Server or by direct querying.
So my question is: What's the best way to get this data into the system? I
can think of two options. Option 1: Ask the PM to manually enter the
attribute information into the custom Sharepoint list that will be the
display of that information. Seems like an acceptable option, but seems
low-tech compared to option 2. Option 2: Create a custom enterprise field on
Server for each attribute and make them be required by the PM upon initial
publishing. I am ok with the PM getting up to 6 required fields as hoops to
go through before publishing. Then, the Sharepoint web part that displays
this key information would be some flavor of a Project Details web part that
is a custom view created to show only the 6 enterprise fields and perhaps the
project end date from line 0 which WOULD be able to dynamically update since
it is driven off the PM's republished schedule. I would then keep the display
depth of the web part to be very shallow, since there'd be only one header
row and one data row for all of this information.
Can somebody validate my thinking and/or recommend an alternate strategy?