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

Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X

custom bom balloon does not show rpt.rel.qty

llam
2-Explorer

custom bom balloon does not show rpt.rel.qty

We have created some custom balloon symbols that shows both rpt.index as well as rpt.rel.qty
The symbol definition shows:

A circle,
within the circle \rpt.index\ (the notation for item number)
Plus, outside the circle, either on top, bottom, left, or right
\rpt.rel.qty\x (the notation for quantity as manipulated by a repeatregion relation)

This results in a circle showing the itemnumber inside the circle and the quantity followed by x (as in times) outside the circle.

Our bom tables are manipulated.
They have a relation that investigates if the model has a parameter length
or if the model is a bulk item
If the parameter length is present then it substitutes the length value as quantity
If the model is of the type bulk then is substitutes zero as quantity

IF ASM_MBR_TYPE == "BULK ITEM" | exists("asm_mbr_length")
\* if model is a bulk item or has a parameter length
IF ASM_MBR_TYPE == "BULK ITEM"
\* if model is a bulk item
Qty=0
\*substitute zero as quatity
ENDIF
IF exists("asm_mbr_length")
\* if model has a parameter length
qty=asm_mbr_length
\*substitute length as quatity
ENDIF
ELSE
Qty=RPT_QTY
\* for other conditions list the standard report quantity
ENDIF

In the table this works like a charme, length parameter value is displayed where needed.

Upon showing balloons in the views however, the quantity for all models is reported as rpt.qty and not rpt.rel.qty

I sort of have a "work around"
I Redefine de symbol definition, remove the \x at the end of the quantity notation
Close the symbol gallery menu
Redefine the symbol again putting back the \x at the end of the quantity notation
Now the balloons do show length values.

Can any of you identify any mistakes in the relation?
Any solutions ?

Seen this behaviour on 2001, WF2 and WF3

Liek Lam
ASM Europe


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
0 REPLIES 0
Announcements
NEW Creo+ Topics: Real-time Collaboration


Top Tags