on 07-09-2009 10:17 AM
When I use save as and save an existing model as a copy, do some small changes, then deploy this new model and export it to our production portal, I see in the export list that the par files of the new model have exactly the same path and id as the same objects in the original model.
How is it possible that these par files coexist without interfering with each other? I don't want to import these new files unless I am sure that the original model is not affected.
Regards
Henning Strand
Hello Henning,
I had also faced something similar , one workaround was to change the name of the
top level object ( i.e. iview ) and then do a save as of the model which wouldnt interfere with the original
Believe that had worked for me.
Rgds
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.