Project Center view filter - field not available

O

oldbradfordian

In Project Server 2007 I have created a number of custom Project Center views
that differ mostly in the fields they display and how they grouping or filter
the project list based on various fields, some custom and some standard
fields.

Everything is OK except for one issue I do not understand.

I have a custom field called "Project Group", which derives its values from
a lookup table. The lookup table has two levels, and it allows multiple
values to be selected. e.g. first level might be 'Trade Show A', 'Trade Show
B', 'Marketing Conference' or whatever, and the second level under each might
be 'Demo', 'Launch', etc.

The field works OK and allows Project Managers to select the appropriate
values for each project (in the Project Properties).

If I add the 'Project Group' field to a Project Center view, so that it
displays as a column in the grid, that works OK too. I can even set a filter
at run-time using the 'Filter' item in the Project Center 'Settings ' menu. I
simply select the 'Project Group' field from the list of fields, then enter
'Contains' and the value I want to filter on, such as 'Trade Show A'.

OK, so all good so far, but there is a problem, which is this:

In the actual view definition (defined under the Server Settings, Manage
Views option), when I try to create a filter for the view (e.g. to show only
projects targeted for 'Trade Show A'), the 'Project Group' field is nto
listed in the list of fields I can select from to create a filter! Even
though the field is included in the fields to display, and the view does
display the column as I stated above, and I can create a filter just like I
want at run-time while viewing the Project Center grid.

Why is this 'Project Group' field not showing up in the view definition
Filter list of fields? I have other custom fields (e.g. Project Risk) driven
by lookup tables that do show up everywhere and work OK.

Any ideas? The view I need to fix is used by our Executive management, and
they cannot accept that they have to re-create the filter manually every time
they want to see this view.

Thanks.
 
O

oldbradfordian

I guess I could, but it just makes for a more clumsy solution overall. The
other downside is that I have to delete the field and re-create it as a
non-multi-value selection field, then every project must be updated and
re-published with the new field.

It still is odd how I can create the filter on the fly in the Project
Center, using the multi-value field, but I can't pre-define the same filter
in the view definition.

Thanks for the advice, Gary.
 
G

Gary L. Chefetz

I quite agree. I've often thought that I could end run this limitation by
stuffing the filter directly in the database, but I've never had occassion
to try. And, of course, this is not supported by Microsoft.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com
 

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

Top