Outline Codes, Cust Fields, and SQL Reporting

[dave]

Hello,

First, I am neither a programmer nor a Project Server Admin, but I
have been given the following dubious task:

We currently use Project Server primarily for task tracking.
Management is looking for numerous weekly reports that join standard
task and project data (project.name, task.name, task.start_date,
finish_date, resource, etc) as well as a myriad of enterprise custom
project and task fields (project.text, project.cost, task.text,
task.flag, etc) and project and task outline codes.

For reporting purposes, I am looking for a way to flag or identify a
task for all of the reports that it should be included in. Initially
I thought a custom task outline code would do the trick. (2 level
task outline code) similar to the following: dept1.report1,
dept1.report2, dept2.report1, dept2.report2, etc..

PM's would flag each task in their respective projects for specific
report(s) using the above outline code values.

However, a single task may be part of multiple reports, so I don't
think this will work?

Any recommendations on how to flag or identify tasks for SQL
reporting?

While I'm here I mine as well as ask my follow up question which is:

Once this is setup, does anyone have any SQL examples of how to
extract custom field and outline code values and descriptors?

Thanks for your help.

Dave

 

[Gary L. Chefetz [MVP]]

Dave:

You need to nail your requirements. Using task-level custom attributes is
certainly one way to seed the database for better reporting, but there are
others as well including project-level and resource-level attributes.

 

[dave]

Thanks Gary:

Our final requirement is to be able to report at the task level with
the distribution method being both Crystal and Excel. My major hurdle
is how to setup tasks so they can be flagged for multiple reports, and
subsequently, how to pull this custom information.

-Dave