Export/Import Problems

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2008 01:30 PM
When Exporting and Importing folders I have run into the following problem. When exporting a space and it's children the "controller xml" may create a fragment like the one below:
Note that the webc
verride and the webc:common my own definitions where webc
verride is a noderef property and webc:common is a file content type.
Please take notice in how it generates the path to the noderef it is referenceing. The webc:common[3] indicates it should point to the cm:meta space and reference the [index] 3 of space. The problem with this is that the system I am importing it into may or may not have the same file at the 3rd index point. Although they DO have the same file name avialable. Therefore, after the import, it references the wrong file.
Is there a way around this? Is there a way to get it to find the correct file based on it's name?
… <cm:folder view:childName="cm:PrivacyNotice"> <view:aspects> … </view:aspects> <view:properties> … <sys:node-uuid>356c26e2-9e98-11dc-98c1-932f43b6caa6</sys:node-uuid> <webc:override>/app:company_home/cm:Programs/cm:model/cm:Template1/cm:meta/webc:common[3]</webc:override> … </view:properties> …
Note that the webc


Please take notice in how it generates the path to the noderef it is referenceing. The webc:common[3] indicates it should point to the cm:meta space and reference the [index] 3 of space. The problem with this is that the system I am importing it into may or may not have the same file at the 3rd index point. Although they DO have the same file name avialable. Therefore, after the import, it references the wrong file.
Is there a way around this? Is there a way to get it to find the correct file based on it's name?
Labels:
- Labels:
-
Archive
1 REPLY 1

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2008 02:07 PM
For those interested I found a way around this although I still question if there is not a bug somewhere.
The node in question had several associated children with the same "childQName". For whatever reason, it did not choose the proper noderef when this was the case. I modified the node to have unique childQName's and it works perfectly. Now it references the child by childQName instead of index number.
The node in question had several associated children with the same "childQName". For whatever reason, it did not choose the proper noderef when this was the case. I modified the node to have unique childQName's and it works perfectly. Now it references the child by childQName instead of index number.
