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

Community Tip - Need help navigating or using the PTC Community? Contact the community team. X

Managing non-Pro/E files in Windchill that were migrated from Intralink 3.x

gchampoux
1-Newbie

Managing non-Pro/E files in Windchill that were migrated from Intralink 3.x

Last year, we migrated from Intralink 3.4 to Windchill Intralink 9.1.
Amongst the Pro/E files, we had many other files that were managed in Intralink.
These include Microsoft Office files and various text/data files.
This included many *.ibl files.
For the uninitiated, IBL files are a PTC invention.
They are text files of coordinate data which can be imported into Pro/E to create daum points, curves, and surfaces.
IBL files are easy to define, and are an easy alternative to using IGES or STEP.


When our IBL files were migrated from Intralink 3.4, they came in to Windchill as CAD Documents, not Standard Documents.
I assume this was because PTC set the default to treat them this way.
However, we cannot replace the primary content as we would with a Standard Document.

We can add these IBL objects to a workspace, roll the revision, and check-out.
And we can download/export the content file.
But we see no way to introduce a replacement content file.
Using only allows importing Pro/E model/drawing files.
Therefore, the File-Open dialog will not display the IBL files, nor allow us to type in the name.


Editing attachments won't work because that is for secondary content (which is empty).


Am I missing something, or have we discoverred a bug?


Gerry Champoux
Williams International
Walled Lake, MI

2 REPLIES 2

Thanks to Dan Wolf for the super-quick answer:


config.pro option:


Tools > "Import to Workspace" only allows importing Pro/E model/drawing files.
Therefore, the File-Open dialog will not display the IBL files, nor allow us to type in the name.


Editing attachments won't work because that is for secondary content (which is empty).


Am I missing something, or have we discoverred a bug?


ShandRonnie
5-Regular Member
(To:gchampoux)

We had to do something similar in order to save back to Commonspace the Pro/Piping linestock files with this configurarion:
allow_import_file_extension stk

Regards,
Ronnie Shand
Top Tags