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

SUMMARY Mass import to intralink

Level 1

SUMMARY Mass import to intralink

All,
Thanks to all who replied.
The general consensus seemed to be IMPORT was the tool of choice. I have discovered that PTC at one time had a BulkLoader tool which they passed on to a partner (Software-Factory, Munchen, Germany). It sounds like it may have potential but am awaiting further information.
Thanks again,
Bruce

Bruce,

I believe you're looking for "mdimpex" using a previously created list
and it will
Actually be an export to mdimpex even though you're going into
Pro/Intralink from
A filesystem. Not sure why PTC implemented the terminology backwards.

Check the knowledge base on the web and let me know if you don't have
access and
I may be able to dig up some notes from the past.

Dan

Bruce,
What you want to do is bring all the part and assemblies files to one
directory, all the drawings to another directory. example: D:\import\models
D:\import\drawings
then create a search path to these locations. add the search path info in
your config.pro.

then create a workspace, object|import, relationship type is to be
"required" toggle to the drawing folder and select either all the drawings
or half of them, then say ok.

This will populate the workspace. Now comes the fun part, you have to
resovle all your conflicts before checkin.

same name exists, ghost files.

I usually delete the ghost files, then update all the files that have "same
name exist"

If a ghost file will not delete,then It may be needed for an assembly or a
drawing, or the part is suppressed in the assy file. If it is suppressed,
then bring the assy up in pro/e and delete the suppressed componant, save
the assy, then delete the ghost file from the workspace.

once the workspace is cleaned up, then you can check in.

hope this helps

Thanks,
Darren Parrillo
Cad Administrator
Brooks Automation
16 Elizabeth Drive
Chelmsford, Ma. 01824
Ph 978-262-2431
Cell Ph 508-958-7011
Fax 978-262-2500
Email darren.parrillo@brooks.com
Bruce,
What you want to do is bring all the part and assemblies files to one
directory, all the drawings to another directory. example: D:\import\models
D:\import\drawings
then create a search path to these locations. add the search path info in
your config.pro.

then create a workspace, object|import, relationship type is to be
"required" toggle to the drawing folder and select either all the drawings
or half of them, then say ok.

This will populate the workspace. Now comes the fun part, you have to
resovle all your conflicts before checkin.

same name exists, ghost files.

I usually delete the ghost files, then update all the files that have "same
name exist"

If a ghost file will not delete,then It may be needed for an assembly or a
drawing, or the part is suppressed in the assy file. If it is suppressed,
then bring the assy up in pro/e and delete the suppressed componant, save
the assy, then delete the ghost file from the workspace.

once the workspace is cleaned up, then you can check in.

hope this helps

Thanks,
Darren Parrillo
Cad Administrator
Brooks Automation
16 Elizabeth Drive
Chelmsford, Ma. 01824
Ph 978-262-2431
Cell Ph 508-958-7011
Fax 978-262-2500
Email darren.parrillo@brooks.com
Hi Bruce,

While the import command would work, it was not intended to be used with
Pro/E items and would take a heck of alot of time.

Simply create a new WS in Intralink and launch a session of Pro/E linked
to this WS. Then navigate to the highest level assembly model and open
it. Once open, click save in Pro/E - you don't even have to make any type of
change to the model. All the items will be saved to your local WS
and are available to be checked into CS once given a folder location.

Hope this helps.

Thanks,
Brad Hacker
ME CAD Administrator
Zebra Technologies Corp.
Cell: 847-770-2507
Office: 847-793-2705
Hi Bruce,
I have done just what your asking. I imported approx. 7,000
Microstation drawings into Intralink using the scripting interface
and a few other programming tools. The script interface allows you
to capture the import process and with additional programming build
a script file to import and potentially add attribute data etc. to
the imported file. I'm not sure what your task is, but initially
find info on the scripting interface. This is a good starting point.

Bob Mills
Engineering Services Manager
Akron Brass Co
Hello all,
I have about 3000 parts and assemblies I need to import in to Intralink.
They are scattered across a couple of Windows workstations and 1 Unix box.
Does anyone have any experience or know of a way to do a mass import of
such a quantity of files. It has been suggested that I just use the Import
command or create trail files to accompish this task but I feel there has
to be a better way. Thanks in advance.
Bruce

Bruce Peters