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

Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X

Upper-level assembly name on repeat region

VR_9713318
8-Gravel

Upper-level assembly name on repeat region

Hello!

To create a report for Fire Certificate Inventory List (EN 45545) I want to use a repeat region of my top-level assembly.

For every part, I need to report the assembly where it is mounted.

Is there any option to report the Part Number (or any other parameter) of the immediate upper level?

I hope the picture below can explain this case better.

VR_9713318_0-1678392151862.png

Thanks!

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
RPN
17-Peridot
17-Peridot
(To:VR_9713318)

I did it with a Repeat Relation.

 

As far I see PTC will do a Depth-first search. And this is only one solution I guess..

 

You must have rpt.level and asm.mbr.name in your repeat region, else you don't have access to the corresponding vars.

The relation will be evaluated not recursively in Creo with a new stack, so the var values will be keept during this while/for Loop.

 

In Level 1 your Parent is empty "" and you save the name in lev1.

In Level 2 your Parent is lev1 and you save in lev2 the name

In Level 3 your Parent is lev2 and you save in lev3 the name

... and so on

 

You must have this for the amount of levels you expect.

 

PARENT is a Repeat Relation Var -> rpt.rel.parent, and must be added.

 

ParentMemberDisplay.png

 

Here this example stops at Level 4, Level > 4 will set a static text, to force a relation edit.

I kept the relation easy to maintain, no "else" 

 

 

 

if rpt_level == 1
  parent=""
  lev1=asm_mbr_name
endif

if rpt_level == 2
  parent= lev1
  lev2=asm_mbr_name
endif

if rpt_level == 3
  parent= lev2
  lev3 =asm_mbr_name
endif

if rpt_level == 4
  parent= lev3
  lev4 =asm_mbr_name
endif

if rpt_level > 4
  parent= "Please Extend Relation"
endif

 

 

 

 

Vars Init

Here you will  only initialize a var if not already exists.

 

 

if !exists ("lev1")
lev1=""
endif

 

 

You can prepend this, for each level, to be sure each level has a value.

But PTC will walk from 1 to 2 to 3 to ...

This may not needed.

 

 

 

The example table is attached.

View solution in original post

18 REPLIES 18

To do this kind of thing with normal parts, I use a parameter in each part/assembly that is something like "partnoASM". In each assembly, I use relations to set this parameter for any components needing it, using the parameter that specifies the "partnumber" for the assembly.

Once I've done that, I can use the parameter in tables/notes.

A couple of difficulties you will have to consider:

(1) A part/assembly can be used in more than one upper level assembly. What do you do then?

(2) If a part/assembly doesn't have the "partnoASM" set, what do you want to have shown?

 

By and large, parts/assemblies do not have any sort of information stored in them that indicates what assemblies they are being used in. There is no way to query a part and show the "next level". Thus, I believe the only way to (possibly) implement what you want is via some sort of custom method like the one I loosely suggest.

Hello, Ken.

Yes, often a P/N is used in more than one assembly, which makes not possible to use your suggestion. Sadly.

Thanks for your contribution.

 

 


@VR_9713318 wrote:

Hello, Ken.

Yes, often a P/N is used in more than one assembly, which makes not possible to use your suggestion. Sadly.

Thanks for your contribution.

 

 


Hi,

I think you can create component parameters instead of part parameters.


Martin Hanák

Hi,

FYI ... described functionality is not available OOTB.

Possible solution: Export table into csv file, import it into Excel and add requested information manually.


Martin Hanák

Hello, Martin.

Reading your and Ken's answer, I understood that I'll have to export the list without this column and create a macro inside Excel to organize these numbers.

Thanks!

Hey.

It was easier than I thought.

I used this formula on column D (ASSEMBLY)

=LOOKUP(2;1/($B$2:B4=(B4-1));$E$2:E4)

Note that I use ";" as separator. Correct to "," if needed.

 


@VR_9713318 wrote:

Hey.

It was easier than I thought.

I used this formula on column D (ASSEMBLY)

=LOOKUP(2;1/($B$2:B4=(B4-1));$E$2:E4)

Note that I use ";" as separator. Correct to "," if needed.

 


Hi,

it is easy in case that your assembly does not contain more than 1 level (this means assembly contains parts, only). In case that the structure of assembly is more complicated adding parent assembly name into additional column is difficult task.


Martin Hanák

Hello.

On my repeat region I used No Dupl/Level and Recursive.

For my case, worked fine, with up to five levels.

VR_9713318_1-1678443364433.png

 

 

 

Hi,

LOOKUP command usage is explained nicely in https://www.youtube.com/watch?v=_eAm7CvXIyU video.

Excel 2021 & Excel 365 user can use XLOOKUP command.


Martin Hanák

Hello!

Good to know.

I checked here, and both sentences work, but it is easier with XLOOKUP!

Thanks for your help.

 

=IFERROR(LOOKUP(2;1/($B$2:B2=(B2-1));$E$2:E2);"-")

or

=XLOOKUP(B2-1;$B$2:B2;$E$2:E2;"-";0;-1)

RPN
17-Peridot
17-Peridot
(To:VR_9713318)

Do you need that for the first level only?

Do you want to include the top level item as well?

VR_9713318
8-Gravel
(To:RPN)

Hello.

For every component, show me the parent, or in more practical terms, show me where each part it is used inside this product.

RPN
17-Peridot
17-Peridot
(To:VR_9713318)

Sure, but do need this multi level or only for the top level, and do you need to have one line for the top level reported? What should happen if you have sub assemblies? Maybe this describes it as well.
We use for find numbers only a repeat region for the top level. And I guess, for your request, top level could be possible.

RPN
17-Peridot
17-Peridot
(To:VR_9713318)

  • image001.pngIs this what you are looking for?
  • Done with OOTB Creo!
VR_9713318
8-Gravel
(To:RPN)

Hello.

Yes, that is exactly what I need!

Could you explain how it is done?

Thanks.

 

RPN
17-Peridot
17-Peridot
(To:VR_9713318)

I did it with a Repeat Relation.

 

As far I see PTC will do a Depth-first search. And this is only one solution I guess..

 

You must have rpt.level and asm.mbr.name in your repeat region, else you don't have access to the corresponding vars.

The relation will be evaluated not recursively in Creo with a new stack, so the var values will be keept during this while/for Loop.

 

In Level 1 your Parent is empty "" and you save the name in lev1.

In Level 2 your Parent is lev1 and you save in lev2 the name

In Level 3 your Parent is lev2 and you save in lev3 the name

... and so on

 

You must have this for the amount of levels you expect.

 

PARENT is a Repeat Relation Var -> rpt.rel.parent, and must be added.

 

ParentMemberDisplay.png

 

Here this example stops at Level 4, Level > 4 will set a static text, to force a relation edit.

I kept the relation easy to maintain, no "else" 

 

 

 

if rpt_level == 1
  parent=""
  lev1=asm_mbr_name
endif

if rpt_level == 2
  parent= lev1
  lev2=asm_mbr_name
endif

if rpt_level == 3
  parent= lev2
  lev3 =asm_mbr_name
endif

if rpt_level == 4
  parent= lev3
  lev4 =asm_mbr_name
endif

if rpt_level > 4
  parent= "Please Extend Relation"
endif

 

 

 

 

Vars Init

Here you will  only initialize a var if not already exists.

 

 

if !exists ("lev1")
lev1=""
endif

 

 

You can prepend this, for each level, to be sure each level has a value.

But PTC will walk from 1 to 2 to 3 to ...

This may not needed.

 

 

 

The example table is attached.

wirro
4-Participant
(To:RPN)

Hello,

 

that's a really good solution - i also tried it.
Have you also tried using a filter on the table?
Unfortunately the behaviour is really...fascinating.

Example:
I changed your relations a bit so i get a parameter displaying "Filter" and it will change between "YES" and "NO".

If i try applying it on the repeat region filter to only show "NO" i get a mixture of both values.

 

Kind regards

MartinHanak
24-Ruby II
(To:wirro)


@wirro wrote:

Hello,

 

that's a really good solution - i also tried it.
Have you also tried using a filter on the table?
Unfortunately the behaviour is really...fascinating.

Example:
I changed your relations a bit so i get a parameter displaying "Filter" and it will change between "YES" and "NO".

If i try applying it on the repeat region filter to only show "NO" i get a mixture of both values.

 

Kind regards


Hi,

is your rpt.rel.filter parameter displayed in repeat region cell?

Please upload your test data.


Martin Hanák
Top Tags