Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations IDS on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Importing parameters to part or assembly 1

Status
Not open for further replies.

xkarlos

Mechanical
Feb 19, 2007
8
Is there a way how to import list of user parameters to finished part ? (any easy way), I do not want to insert them one by one. I need insert the same parameters to about 100 parts.

Thanks for every help !!!
 
Replies continue below

Recommended for you

Mapkey is your best friend here.

-Hora
 
I have a text file of various paramater sets that I drop into relations. Exit relation. Reopen relation and delete the previous text. The values will be added to the paramter list
Example:

step 1:

put the following into "relations"
(copied from text file works well to reuse the values)
DESCRIPTION1="X"
DESCRIPTION2="X"
PART_NO="X"
DWG_NO="X"
MODELED_DATE="X"
MATERIAL1="X"
MATERIAL2="X"
PAINT="NO"

step 2: save and exit relation
step 3" reopen relations
Delete all the text you place in step 1

Step 4: edit the values in parameter window

I hope this helps
 
Thank you very much guys !!
This is exactly what I was looking for !

 
also it looks like you can use pro-batch to play a trail file into existing files

create trail file - do your parameters.. save the trail as .txt file then run pro-batch with the argument in the pro/engineer command box proe.bat myprams.txt and use upgrade

would like some feedback if this will fly....because then you wouldn't have to open each file...set pro-batch to do it and go get a cup or two of coffee :)
 
It looks like kgrzebien's method works for string parameters. But what about integer parameters? Logical (Yes/No) parameters?

Our company uses a Yes/No parameter to signify whether a model entity should be included on the automated BOM. There are many times when an item is in (and will stay in) the model for design purposes only and will not appear on the BOM.

We also use an integer parameter called 'YEAR' to capture the year the part was created.

Is there a way within the relation to tell Pro/E what kind of parameter is being read in?



Tunalover
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor