Custome Enterprise Field Names In OLAP

M

mark.everett

We revised enterprise custom field names to a new standard, using a
leading underscore and lower case e (_e) to force them up the list,
group them, and show them as being "enterprise". Underscore does not
appear to be an illegal character. When the cube runs, the field
values update, but the names reverted to their enterprise field names
(Enterprise_Resource9, etc).

The IT people say that OLAP shows errors. Can we do something to
change the field names to their friendly name, as they were? The field
names seem to work in Project Pro and in PWA. We are using 2003
Project Server.

Thanks in advance,
Mark
 
D

Dale Howard [MVP]

Mark --

Using the underscore character is fine for Views, Tables, Filters, Groups,
etc. as the character forces the item to the top of the menu. I don't
recommend you use the underscore character in the names of custom enterprise
Fields, however, as this could very well be the source of your OLAP errors
and Portfolio Analyzer problems. Hope this helps.
 
M

mark.everett

Dale -

Thanks for the input and I will rename some of them to test. However,
the underscore character is used in the default field names, so if that
is the issue, it's inconsistent.

Mark
 
M

mark.everett

Follow Up: The leading underscore works in PWA and Project Server with
no problem. However, Analysis Services doesn't seem to like a leading
underscore. I changed some names back to using just a leading "e" and
those field names changed to a friendly name in the Field List. I have
changed the remaining fields also to eliminate the leading underscore.
 
Top