Field Definitions

[patcapps]

Can we keep a set of 130 field different definintions locally

 

[Reid McTaggart]

There are 260 local custom fields in total. Whether there are enough of the
types you need is another matter.

--
Reid McTaggart
(e-mail address removed)
Alegient, Inc., Houston
Project Server Experts
Microsoft Certified Partner

 

[patcapps]

Thank you for your response. Am I correct in assuming that projects saved
from Project Pro to Project Server must use the same filed definitions as
those I define in Project Server?

 

[patcapps]

Please note my typo on my previous response. "filed" should be "field"

 

[Reid McTaggart]

Not exactly, if I understand your question.

There are 260 local fields that are NOT defined at the Enterprise level.
Those fields are do not have to match up with anything. They can be
completely unique to an individual project plan.

Separate from those local fields are the Entrerprise fields. Enterprise
field definitions are controlled at the enterprise level, and all projects
saved to the server WILL comply. You don't have to do anything to make this
happen. That's one of the beauties of Project Server: Enterprise standards
are enforced, but local flexibility remains.

--
Reid McTaggart
(e-mail address removed)
Alegient, Inc., Houston
Project Server Experts
Microsoft Certified Partner

 

[jonathan_sofer.....]

Pat,

Reid makes a good point in the advantages of server being that
standards are enfored but the flexibility at the local level still
remains. You will not lose any of your local field definitions or
values or any views that have been defined at the mpp plan level.
These will be stored on the server but only against the individual plan
it came over with. You do have to make sure that none of your local
field, tables, views, filters, groupings etc. have the same name as an
enterprise global one. This will cause a conflict and will force you
to replace or rename your local item.

You can also migrate data from local fields to enterprise ones during
the import process.

Jonathan Sofer

 

[patcapps]

Thank you very much. Your response tells me why I had painstakingly (through
ignorance) had to choose enterprise field names while saving projects to our
Project Server. Our top management wants some consistencey (in field uasge)
so we can use Project with other software (e.g. MPM) and also so different
managers won't have to decipher field usage when managing different projects.