800xA import/export problem
Hi
I have an issue with an 800xA system.
It consist of two very similar projects. Project A is completed and was exported to an off-site engineering station.
This export was then changed (renamed I think) to Project B. The applications was then modified to suit project B (FB names, HW etc.), and now I would like to import B into the main system where A already exist.
I cannot get this to work. Project B wants to replace A even though the project and application names are different. I have tried to import just one application but get same thing. It wants to replace the existing application.
I have even tried to delete A and import B, then import A back into the system. Now A wants to replace B! I'm very confused.
What have I done wrong and how can I fix this?
Thanks for your time
I have an issue with an 800xA system.
It consist of two very similar projects. Project A is completed and was exported to an off-site engineering station.
This export was then changed (renamed I think) to Project B. The applications was then modified to suit project B (FB names, HW etc.), and now I would like to import B into the main system where A already exist.
I cannot get this to work. Project B wants to replace A even though the project and application names are different. I have tried to import just one application but get same thing. It wants to replace the existing application.
I have even tried to delete A and import B, then import A back into the system. Now A wants to replace B! I'm very confused.
What have I done wrong and how can I fix this?
Thanks for your time
Asked 10 months ago
Answers
2
I think what you are doing is not possible.
You can rename the project but the 'under laying' GUID doesn't change.
Answered 10 months ago
0
The problem as already answered is that once the project is created, the GUID doesn't change even if its renamed.
You can try doing this and see if it works.
1) Create Project B (just an empty project) in the system where you want to import.
2) Import Applications of original project B by manually placing them under this newly project B.
3) if it asks for dependencies, then you many need to import the dependencies first before importing the applications. (Do not do Import all).
You can not import whole of the project but importing by parts should still work if you create a new project.
You can try doing this and see if it works.
1) Create Project B (just an empty project) in the system where you want to import.
2) Import Applications of original project B by manually placing them under this newly project B.
3) if it asks for dependencies, then you many need to import the dependencies first before importing the applications. (Do not do Import all).
You can not import whole of the project but importing by parts should still work if you create a new project.
0
All the answers so far are correct: the underlying GUID for an object or application etc has not changed, but just changing it's name. However, given you "moved" the project to an offline engineering system, you can change the GUID. This is usually done by copying an object. When copied the object (or application or even Aspect) will have the same properties of the original (including name) but will have a new GUID. This is obviously a little more complicated for code but the same principle applies. Once copied you can rename as needed the new "copied" items. Once this is done, there will osme additonal work as a lot of the copied objects/Aspects will have references back to the original Objects and these need to be changed to the newly copied items. Obviously, the newly copied items should be put into their own separate structures, so they can be easily identified. Once all this has been done, you can export/import this new "system" back into your original system project. :-)
Add new comment