Conflict between Global properties and Local Properties

[Maleza]

I would appreciate any help with this situation:

1. I created a project within the enterprise environment
2. At some point I saved the project as a file using File/Save As
3. I deleted the original project from the Server
4. I re-imported the "saved-as" project back to the Server after
making some changes

My problem is that during the "Save As", I was given options to bring
along the global items. Later when I import the project back to the
Server, I get all kinds of errors (when opening the project back in the
Server environment) saying that there are conflicts between the
filter/table/group names in the Server and the local file I imported.

It seems as though the loaded global items in the imported file are
viewed by the Server as local items (as opposed to global items that
came from the Server in the first place).

I suppose it is better to just stay in the enterprise environment
without doing a "Save As", but does anyone know of a way to deal with
this if you need to do a "Save As". It is pretty frustrating.

Thanks.

 

[Jonathan Yong]

You can goto Tools -> Organizer, from there you can remove the
View/table or whatever thing that Project complaint about from your
project and add back the equivalant View/table or whatever from the
Global item to your project.

 

[Gary L. Chefetz [MVP]]

Maleza:

Regardless of how you bring the project back into the server, there's some
risk of this happening. This is one of the reasons why we don't recommend
taking projects in and out of the Enterprise database without good cause.
When the errors come up, click the rename button, and give these objects
names like "X" then XX then XXX and so on. Then open the organizer from the
tools menu, and hunt down the renamed objects and delete them. That will fix
the problem.