Skip to main content
1-Visitor
July 9, 2014
Question

Copy Paste Folder Structure

  • July 9, 2014
  • 15 replies
  • 7159 views

I am implementing Windchill in a customer which wants to have the same folder structure replicated in every first level folder, what's the easyest way to achieve this.


Once they have "|" in the name of numerous folders I can't create the folder structure in windows and then import to Windchill...



Guilherme Rocha


15 replies

MarcoTosin
21-Topaz I
21-Topaz I
July 10, 2014

Guilherme,


if you use templates you are able to create a new product or library with the same structure, as you can see on attached image.



Marco

Marco
1-Visitor
July 10, 2014
Marco,

This is a question I’ve also had. I have found that works well for the first series of folder/ Sub-folders. But what if you have the need for another instance of the same folder/ Sub-folder series? In ProjectLink I can load a zip file with the folders and sub-folders but I don’t have that functionality in PDMLink.

A beer to the

Bob Lohbauer
18-Opal
July 10, 2014
If the contexts already exist you can create a folder structure on a local disk and then use the "Upload from compressed file option" to get the folder structure into Windchill.

-marc


1-Visitor
July 10, 2014
Marc,

I tried it and it worked if I had some piece of data in one of the folders. If you need to simply Create an empty folder structure you just need to put a dummy file into one of the folders.

Bob Lohbauer

1-Visitor
July 10, 2014

  • If you are working in product and libraries, you can use a template to recreate the folder structure. See CS129445


  • If you are working in projects or programs (ProjectLink), you can use the Export to File action and only select "Folder Structure" in the export options. See "Exporting a Project or Program"


  • If you want to recreate folder structures within the same context, or within existing products and libraries, then there is a workaround that is slightly tedious depending on how many folders you're working with.


    1. Ensure each folder one document within it that has been created from a local file. If they don't, upload a placeholder document with a unique name. For example, "StructureABC.txt" and then copy and paste it into each folder and subfolder.

      This is the tedious part, but theoretically you'd only need to do it once. If you are using desktop integration, you can do this really quickly from Windows Explorer. (For all folders except for the ones that include a restricted character in the folder name.)


    2. Select the top folder and the perform a Download Documents to Compressed File operation. Make sure you select the following options: Include contents of subfolders and Save full path information


    3. This creates "document_contents.zip" to save locally. If you open in, the folders with restricted characters ("|") are hidden, but that's ok.


    4. Navigate to where you want to duplicate the folder structure and perform the Upload Documents from a Compressed File operation. Make sure you select the Use folder names checkbox.


    5. This will recreate the structure of all folders that had a document saved within it.


    6. Perform a global search for the placeholder document ("StructureABC.txt" in this example) and then use the Search Results table to delete all instances of that document at once.


18-Opal
July 10, 2014
I was thinking there was a catch that needed to be worked around…
18-Opal
July 10, 2014
Caitlin,

I was told by PTC tech support that the Export to File from a project was intended to go from one Windchill system to another. I was running into some issues with using that to update the folder structure of some projects and ran into some issues. I don't remember the exact issues now, it was several months ago.

-marc


1-Visitor
July 10, 2014

I'm not aware of any limitation that would make an import/export operation work correctly between two systems and then fail between projects on the same system. Especially if you're just doing a simple folder structure.


You're not supposed to use it between major releases (e.g. don't export info from a 9.1 system and try to import it into 10.2). There might also be issues trying to import/export between Classic project templates and EPP ones. But in a fresh Windchill install, for the purposes of taking one empty folder structure and recreating it in another project -- there should be no problems whatsoever.


I'm actually working on getting dev to review/define/update all those options that appear in the various project Import/Export windows. If you remember what your earlier issues were, let me know and I can try to roll those questions in next time I harass the development team about it.

grocha1-VisitorAuthor
1-Visitor
July 11, 2014
I think I was not clear, windchil doesnt allow me to copy paste empty folders to reproduce The structure, thats The main problem.
Some time ago Ive cheated on that creating a fake file and copy pasting it to all folders in The structure, used The download to compressed file function to download The structure to Windows and then used The create from compressed file function multiple times to reproduce The folder structure multiple times, in The end I made a search and deleted all The resulting fake files.
I cant do that now because in windchill The folder names have The pipe symbol, as Windows doesnt support it in folder names, it replaces it with The underscore symbol, now The downloaded structure cant be imported because it has The wrong folder names.
I ended up creating all The folders manually, took like one hour to do it, if there was an option to copy and paste folders in windchill it would take like ten minutes.

Os there other options to do it?
1-Visitor
July 11, 2014

Hello



I am not bringing any new technical solution as everything has been said. I am just wondering of the need of so many folders and sub-folders. Does your customer know that folders in any PDM are not designed to sort the data but for access permissions ? I feel that your customer is trying to replica is legacy data management (surely based on Windows Explorer) and he is creating a hell of a nightmare to administrate all this.



I recall when we implemented Windchill in my company. We focused on our product so got the people to access to work product centric rather than site centric. For our tooling departments, well, my team could not be on every battle. so we let them with their tens/hundreds folders. Even if the folders have all the same access permission, guess what happened. The new staff quickly checked in all the CAD in the same top level folders, and those who wanted all those folders ended up doing the same !!!



Of course I do not know the particular reason of your customer and work from assumption based on my experience and I am really interested in knowing why as I have never met a reason to create any sub folder in Windchill except for keeping a Windows Explorer type structure.



Best regards