cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Automatically Add Formats to Workspace (or "Don't create ghost objects for things that already exist!")

Automatically Add Formats to Workspace (or "Don't create ghost objects for things that already exist!")

When a part or assembly is added to a workspace on the fly (on demand), the format is not included, even though it is required by the drawing.  This happens even if the default collection preference is set to "Required".

These collection preferences are being ignored for on-the-fly retrieval of files by Creo.  This behavior leads to ghost objects being created in the workspace anytime a part or assembly is duplicated in Creo without first adding the format to the workspace.  It also makes it nearly impossible to use Creo part (or assembly) templates with a drawing already associated to them since every time you use one another ghost object is created.

The workaround is to either manually add the required format to the workspace in advance, or manually open the drawing in Creo (so it will pull the required format) before duplicating the part (or assembly).

Windchill is obviously smart enough to know the drawing has a dependency on the format (hence the creation of the ghost object).  It should be smart enough to automatically add the missing format to the workspace on the fly (just like it does for any other Creo dependency.)

Related tech support article:  https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS5822

Related discussions:

9 Comments
tdowney
Participant

Just a thought.  I think the Formats have to be in the same folder or a subfolder in order for them to be called by a template.

TomU
Emerald II

This behavior is not specific to templates.  (We have our templates in the same location as our formats.)  It's a fundamental collection problem.  "Required" should do just that - bring everything required.  It does not.

BenLoosli
Sapphire II

I am not seeing this problem in Windchill 10.0 m040.

I have my formats in Windchill and on disk and my drawing templates on disk.

Formats are NOT in the same folder as the templates.

When I select a drawing in Windchill and then Add to Workspace, select a workspace, I do not set anything and I get the part, drawing and format downloaded to my workspace.

Please state what version/build of Windchill you are seeing this issue with.

TomU
Emerald II

You are correct.  The "Add to Workspace" piece works fine.  It's the "on the fly" behavior that is a problem.  I've updated the idea to clarify this point.  Thanks.

BenLoosli
Sapphire II

Not sure I understand your 'on the fly' scenario.

If I open a drawing file from Creo, I get the format in my workspace, along with the part and drawing files.

If I Select the drawing in Windchill and Add to Workspace, I get the drawing, part and format files.

Can you give a sequence of steps that can be duplicated?

TomU
Emerald II

There are two links in the product idea.  They both list the steps necessary to reproduce the problem.

BenLoosli
Sapphire II

I see it now.

I guess we don't see it here since our designers almost always have drawings and formats in their workspaces.

PTCModerator
Topaz I
Status changed to: Acknowledged
 
SvenR
Aquamarine

The Fix for this Issue would be very helpful because if there is a ghost object (.fmt) then this can lead to problems uploading files to the server. Because those are associated via multiple hops with this file. Those files fail to upload, too, and then the user cannot continue to work on another workstation despite 'universal upload'.

Example: open xy.prt and save a copy (with associated drawings). Then create a new ASM and assemble the new .prt file. Then save all files (Ctrl+S). Result: the upload fails also for the assembly because of the ghost-objectish .fmt file.

This can manually be resolved by updating the .fmt-file ghost object with the actual file from Windchill.

Expected behavior would be: upload .asm file to the server regardless if the .fmt file coresponding to a part that is included in the assembly is associated with a ghost object.