Using "_"prefix for different objects in the database?

[anovak]

A reputable service firm we all know and respect suggests that we use
"_" (underscore) as a prefix for new table names, view names, group
names, etc. in order for the user-defined ones to be sorted together.

Anything wrong with following approach with lookup table and custom
field names?

What about for user-defined security groups, etc.?

I DID get an error when I tried to prefix a field we have called
"Funding Authority" with an underscore:

"The custom field could not be saved due to the following reason(s):
The custom field name is not valid. The custom field is used as an
OLAP cube measure or dimension and is not valid in that context. Make
sure the name is valid for OLAP and that the custom field, calculated
measure and
Project Server built-in cube object names are distinct from each
other."

But it was OK to use "unts_" (University of North Texas System) as a
prefix.

Any tips?? Would just seem to be easier for all the custom fields to
be sorted together for inclusion in PWA views, etc.

Thanks,
Andy Novak
UNT

 

[Ben Howard]

Hi Andy,
a custom field with an _ will not be able to be added as a dimension to the
cube.
An _ for ProjectPro views etc shouldn't give any issues from a technical
perspective. However, I don't bother trying to group these sort of things by
using an _ or anything else, I just name them well and define them well so
that users get value out of them, and I cut them down substantially, most
users will only use 3 or 4 anyway! - the key is in identifying them.

 

[Dale Howard [MVP]]

Andy --

That reputable firm would be us, msProjectExperts. This advice is only for
custom View, Tables, Filters, and Groups in Project Professional and for
custom Views in PWA. The reason for this is because it forces the custom
objects to the top of the appropriate menu. I see no sense in using the
underscore character for anything else, which is what you have done, and
which causes you problems. I agree with Ben Howard's advice, which is to
name objects like fields with meaningful names. Hope this helps.

 

[anovak]

Andy --

That reputable firm would be us, msProjectExperts. This advice is only for
custom View, Tables, Filters, and Groups in Project Professional and for
custom Views in PWA. The reason for this is because it forces the custom
objects to the top of the appropriate menu. I see no sense in using the
underscore character for anything else, which is what you have done, and
which causes you problems. I agree with Ben Howard's advice, which is to
name objects like fields with meaningful names. Hope this helps.

Sounds like good common sense.