Skip to main content
D
dgschaefer21-Topaz II
21-Topaz II
May 11, 2010
Question

&model_name

  • May 11, 2010
  • 20 replies
  • 9576 views
if your note has a leader, and that leader is attached to an edge or
surface that belongs to the part in question (not an edge created by a
cross section, that edge belongs to the assy), then you can use the
following:

&model_name:att

The 'att' suffix tells Pro/E to look in the model that the note is
attached to. You have be certain that your note is attached to an edge
belonging to the model you want, however.

Doug Schaefer

20 replies

Show previous replies
D
DarrinHiebert1-Visitor
1-Visitor
May 12, 2010
I just verified this here as well, that a different parameter, like part_name works. We have always used &part_name, and not model_name. :att works, but Pro changes the note callout to &part_name:att_mdl when you're done. I don't know if it's a good practice to get into adding :att_mdl, or not, but currently either one works...

Verified on WF 2 and WF 5 (M030)...
M
MartinBrown1-Visitor
1-Visitor
May 12, 2010
Hi All
I have yet to figure out how to touch a part in an assembly drawing and pull the "file name" into a note. You can pull a parameter value (we use a parameter called PART_NUMBER) by attaching a note &part_number:att - but this has been said already.

If you want the "file name" this is one way to get it, &model_name:(session_id)

The problem is getting the session id and this is a free floating note. It does not have to be attached to anything, but if you are careful you can get most of what you need by attaching the note to the right part in the drawing...

The session id may be obtained thru the relations window in a drawing.
TOOLS
RELATIONS
"look in" PART
select a part
SHOW
SESSION ID
PART
start selecting parts and write down the numbers on a paper copy of the same drawing.

Works well in WF4 M092

enjoy

Martin T. Brown
Design Specialist
Merrick & Company
Direct: 865-241-4642
www.merrick.com
L
lylebeidler1-Visitor
1-Visitor
May 12, 2010
Just my 2cents.

I tried it in wf3, and model_name does not work, but any parameter does.



I tried &model_name:att and &model_name:att_mdl (and oodles of variations
with capitalization & not)



Neither worked.



It sounds like &model_name:att works fine for Doug, but not for me or Bob.

Could the difference be being linked to an Intralink session? Doug, are
you running linked to Ilink? How about you Bob? I am, and it's not working
for me.



However, if I find out the session id of the part, and create the note
&model_name:<session id=">, it works fine.



--



Lyle Beidler
MGS Inc
178 Muddy Creek Church Rd
Denver PA 17517
717-336-7528
Fax 717-336-0514
<">mailto:-> -
<">http://www.mgsincorporated.com>
R
rrich1-Visitor
1-Visitor
May 12, 2010
All,

Facts and other stuff on this.

In WF4 M100

¶meter_name_of_choice:att produces ( parametervalue) of part
attached to. Note this parameter_name_of_choice must be a user created
parameter(not system parameter) located in the part you are attaching to.
However review of note after shows this ¶meter_name_of_choice:att _mdl
as Doug pointed out below. I tested this and it worked fine with a
parameter in my part called DESCRIPTION. Note showed proper description to
whatever part I was attached to. Changing the attachment point to another
part instantly updates the note.



PTC why doesn't this work with &model_name which is a valid system
parameter?



&model_name:place_ID_number_here produces (model name) of ID number you
placed. Possibly attached to the wrong part if you do not have the right ID
# for the part. This is not convenient if you have a large number of
components you have to guess at the ID or add dimensions and search for IDs.




Ron


D
dgschaefer21-Topaz IIAuthor
21-Topaz II
May 12, 2010
Actually, I got the same results as you. I had assumed on the original
question that he was referring to a user parameter, not a system
parameter. I didn't catch that it was a system parameter until later.

So, user params work, system params don't for me, same as you. 😄 Oh,
and I'm not on Ilink, so that's not a factor.

Doug Schaefer
D
dustin1-Visitor
1-Visitor
May 12, 2010

I actually ran into a similar issue a while back. I was trying to create text that would be attached to the model. The model_name parameter was not sufficient automatically put the correct text in place. So I created a user parameter "NAME" as other's have suggested here, and then created a relation:

NAME=rel_model_name

With this format, you could use &NAME:att for your note, and you wouldn't have to update the user parameter "NAME" for each model. I only have one type of part setup this way, so most of my parts are not setup right for this.

R
rollinsn1-Visitor
1-Visitor
May 12, 2010
Dustin,

This is a pretty easy solution. I am considering adding this relation
to our start part. Thank you.

Does any one know where the "toggle dims" button is in WF5?

confounded ribbon...

Thanks...

Nate
R
rollinsn1-Visitor
1-Visitor
May 12, 2010
I found it -

Annotate > parameters > Switch dimensions

"RightUnderMyNose" syndrome...

Thanks all.
G
GavinBRumble10-Marble
10-Marble
May 15, 2010
This :att secret has really tweaked my interest.just how long has this been
around?



By the way, there is an easy way to get the model name (filename) into a
user defined part parameter using a relation in your start parts.

Filename = rel_model_name()

This could obviously be "partnumber", "item_number", or whatever you like.



Inexplicably, this ALSO works:

model_name = rel_model_name()

.which means that I was able to override the system parameter. The drawing
note (&MODEL_NAME:att) was happy.



This works in WF3, WF4, WF5.



Gavin B. Rumble, PE

Solid Engineering

336-224-2312


D
dgschaefer21-Topaz IIAuthor
21-Topaz II
May 17, 2010
I know it was in WF2, might have been in 2001, I just don't remember
when I started using it.

Doug Schaefer
Terms & ConditionsCookie settingsAccessibility statement