topic Export/Import Problems in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/export-import-problems/m-p/170872#M124137 <HTML><HEAD></HEAD><BODY><SPAN>When Exporting and Importing folders I have run into the following problem.&nbsp; When exporting a space and it's children the "controller xml" may create a fragment like the one below:</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE>…<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;cm:folder view:childName="cm:PrivacyNotice"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;view:aspects&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; …<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/view:aspects&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;view:properties&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; …<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;sys:node-uuid&gt;356c26e2-9e98-11dc-98c1-932f43b6caa6&lt;/sys:node-uuid&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;webc:override&gt;/app:company_home/cm:Programs/cm:model/cm:Template1/cm:meta/webc:common[3]&lt;/webc:override&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; …<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/view:properties&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; …<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><SPAN>Note that the webc<img id="smileysurprised" class="emoticon emoticon-smileysurprised" src="https://connect.hyland.com/i/smilies/16x16_smiley-surprised.png" alt="Smiley Surprised" title="Smiley Surprised" />verride and the webc:common my own definitions where webc<img id="smileysurprised" class="emoticon emoticon-smileysurprised" src="https://connect.hyland.com/i/smilies/16x16_smiley-surprised.png" alt="Smiley Surprised" title="Smiley Surprised" />verride is a noderef property and webc:common is a file content type.</SPAN><BR /><BR /><SPAN>Please take notice in how it generates the path to the noderef it is referenceing.&nbsp; The webc:common[3] indicates it should point to the cm:meta space and reference the [index] 3 of space.&nbsp; 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.&nbsp; Although they DO have the same file name avialable.&nbsp; Therefore, after the import, it references the wrong file.</SPAN><BR /><BR /><SPAN>Is there a way around this?&nbsp; Is there a way to get it to find the correct file based on it's name?</SPAN></BODY></HTML> Mon, 19 May 2008 17:30:15 GMT nyronian 2008-05-19T17:30:15Z Export/Import Problems https://connect.hyland.com/t5/alfresco-archive/export-import-problems/m-p/170872#M124137 When Exporting and Importing folders I have run into the following problem.&nbsp; When exporting a space and it's children the "controller xml" may create a fragment like the one below:…&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;cm:folder view:childName="cm<IMG id="smileytongue" class="emoticon emoticon-smileytongue" src="https://migration33.stage.lithium.com/i/smilies/16x16_smiley-tongue.png" alt="Smiley Tongue" title="Smiley Tongue" />rivacyNotice"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;view:aspects&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; …&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/ Mon, 19 May 2008 17:30:15 GMT https://connect.hyland.com/t5/alfresco-archive/export-import-problems/m-p/170872#M124137 nyronian 2008-05-19T17:30:15Z Re: Export/Import Problems https://connect.hyland.com/t5/alfresco-archive/export-import-problems/m-p/170873#M124138 <HTML><HEAD></HEAD><BODY><SPAN>For those interested I found a way around this although I still question if there is not a bug somewhere.</SPAN><BR /><BR /><SPAN>The node in question had several associated children with the same "childQName".&nbsp; For whatever reason, it did not choose the proper noderef when this was the case.&nbsp; I modified the node to have unique childQName's and it works perfectly.&nbsp; Now it references the child by childQName instead of index number.</SPAN></BODY></HTML> Wed, 21 May 2008 18:07:06 GMT https://connect.hyland.com/t5/alfresco-archive/export-import-problems/m-p/170873#M124138 nyronian 2008-05-21T18:07:06Z