DominicG
Aerospace
- Sep 23, 2004
- 57
I have a weldment assembly that is made up of W-Flanges from the Content Center. Most of these W-Flanges feature copes or special cuts at one end or another. So they need a discreet part number in order to keep track of them. At first the Content Center seemed like a Godsend due to the ease of use. The problem arose when I attempted to rename these Content Center Parts.
The typical procedure that I use when building such an elaborate assembly is flesh out the design, get it finalized (somewhat), and then rename the parts to dash numbers of the original assembly. For example, the assembly is called “6015-015.iam”. The filename for the first second and third parts in this assembly are 6015-015-01.ipt, 6015-015-02 ipt, and 6015-015-03 ipt. I find this naming convention particularly useful when viewing a file list of a directory. Without much effort you can identify which files that belong to a particular assembly.
However, the problem arose after I needed to rename several of the parts from the content center. I would open the assembly and select a component. I would then open the component, save as a new name and then close the file. Back in the assembly, I would then replace the old component with the one I renamed (I realize that this is a long hand way of doing this, and that there is an easier way through the Vault. But it suits the purposes of the discussion).
When I “Save as” with a part from the Content Center, it acts like the operation worked. There is even a new file made which can be seen in the browser. However when you go to use this file in your assembly, it inserts the OLD Content Center File! Attempting to open the new filename yields even stranger results. When you open the new file, the OLD file opens instead. No amount of computer gymnastics using Windows Explorer or File manager can circumvent this issue. Believe me, I tried.
So I have a large assembly that has several dozen parts with file names that do not comply with company standards (as well as my own) and that I cannot rename. How can I remedy this? Until I get around this issue, I have advised other users in my group to not use ANY files form the Content Center.
Thank You,
Dominic Greco
The typical procedure that I use when building such an elaborate assembly is flesh out the design, get it finalized (somewhat), and then rename the parts to dash numbers of the original assembly. For example, the assembly is called “6015-015.iam”. The filename for the first second and third parts in this assembly are 6015-015-01.ipt, 6015-015-02 ipt, and 6015-015-03 ipt. I find this naming convention particularly useful when viewing a file list of a directory. Without much effort you can identify which files that belong to a particular assembly.
However, the problem arose after I needed to rename several of the parts from the content center. I would open the assembly and select a component. I would then open the component, save as a new name and then close the file. Back in the assembly, I would then replace the old component with the one I renamed (I realize that this is a long hand way of doing this, and that there is an easier way through the Vault. But it suits the purposes of the discussion).
When I “Save as” with a part from the Content Center, it acts like the operation worked. There is even a new file made which can be seen in the browser. However when you go to use this file in your assembly, it inserts the OLD Content Center File! Attempting to open the new filename yields even stranger results. When you open the new file, the OLD file opens instead. No amount of computer gymnastics using Windows Explorer or File manager can circumvent this issue. Believe me, I tried.
So I have a large assembly that has several dozen parts with file names that do not comply with company standards (as well as my own) and that I cannot rename. How can I remedy this? Until I get around this issue, I have advised other users in my group to not use ANY files form the Content Center.
Thank You,
Dominic Greco