user field for "anything"

[anovak]

Some of my users want a project-level custom field that anyone can use
for anything. This is exaggerated, but one user can use it to sort
their projects only by credit card #, one user can sort theirs by room
number, etc.

My data administration hat is burning right now, but is this even sort
of OK to do - have a User Field where anything goes?

Thanks,
Andy Novak
UNT

 

[Jonathan Sofer]

Where would this sorting take place? If it is in PWA then I imagine the
sorting would not work so well if your users are using the same field to
store different data.

 

[anovak]

Where would this sorting take place? If it is in PWA then I imagine the
sorting would not work so well if your users are using the same field to
store different data.

But they would only be looking at their projects at the time (filtered
by way of the functional security within Project Server).

 

[Jonathan Sofer]

I can't think of any technical reason why they can't have a field like that.
Normally when a PM wants to use something specific to their project, I would
have them use local fields, views, table etc. But in the case of a project
level field, this obviously does not exist locally plus can't be used in
PWA. I can see why it might be a viable option to have.