Issue with views when opening projects

B

Brian

The way we have set up our enterprise, people start new
projects by selecting templates in the Enterprise
Templates tab. All goes as expected when saving. The issue
happens when they close project and reopen the project. At
that point, they get several messages that "the enterprise
global already contains a view called Resource Usage." It
asks whether to replace it with the one from enterprise
global, replace all items with duplicate names, or rename
the view in the project. Any advice on which I should do?
What is the best way to keep these messages from coming
up?

I also get messages for three views (Data Entry, Task
Form, and Entry) that there's a view in the project that
cannot be overwritten. I'm supposed to click OK to rename
them. Usually, I just add a 2 after the name so that I can
move on, but is there something I should be doing instead?
I would like for users to see as few messages as possible.

Thank you very much.
Brian
 
G

Gary L. Chefetz [MVP]

Brian:

See the following for a general explanation of what's happening:
http://www.projectserverexperts.com/Project Server FAQs/cantoverwritetable.htm

These errors are usually an indication of pollution in the Enterprise
Global, HOWEVER, I have seen this behavior when using Enterprise Templates,
but have not been able to isolate the whys of it. Theoretically, when you
rename the objects, you should then be able to open the organizer, find them
and delete them. If you're seeing the behavior I've seen, they're simply not
there when you open the organizer and the problem seems to go away after the
first time you rename them. If you can confirm that this is the behavior
you're seeing, let me know so I can cite your circumstance in a bug report.
 
G

Guest

Hi Gary,
Thank you for your response. I seem to have a hybrid of
what you mention below. After following the instructions
on the link you provided, I tried saving a new project,
closing Project, and reopening. I still get the same
messages and end up adding a 2 after each view name.
However, once I close and reopen again, I don't get the
error messages anymore.

I could tell users to just rename the first time, knowing
the problem would go away. My worry, though, is that the
user will think the program (or me) is half baked.
-Brian
 
Top