Renumbering multi-level component balloons

[ccyokes]

I'm working on a product build that has a left and right primary section that get bolted together at the end of the build (split for shipping size restrictions) and have made the file with a subcomponent for each half for organizational purposes. The roof for each half is further split into multiple pieces due to material size limitations.

Now when making the parts list in the drawing, I seem to be unable to renumber the lid because the balloon identifier only supports "first level" and "last level" renumbering. No second level or anything between. If I renumber a component to 1.1, then the roof balloons grey out with a lock icon as they are three levels deep (1.22.1) and I'm renumbering a component with only 2 levels. However, if I click on the roof to start, I cannot change the "22" part, only the first position or last. See screenshots. 

My assumption would be to simply type in the number I want to apply instead of having to select which level I want to change. But that does not work. (neither does 1.14.1)

As there is only one part I am unable to renumber, I could set 1.1 to be 1.14 temporarily, then renumber it directly to 1.22 to force those two to swap numbers, then change 1.22 back to 1.1. But this would be quite the cumbersome workaround if you have many third level components and would be exponentially more effort if you have any at fourth level or beyond.

Yeah, that works here. But how do I deal with (or avoid) this in the future in a better way other than simply not using subcomponents?

[Pramod.kadam]

Hi @ccyokes ,

Thanks for posting and explaining the workflow in detail. 

We can renumber first level or leaf level numbers for the balloon. So if we want to renumber 1.22.1 to some other number like 1.23.1, then we have to renumber 1.22 to 1.23 so that all the components under 1.22 are grouped under 1.23. So in this case, 1.22.1, 1.22.2 will become 1.23.1, 1.23.2.. 

Thanks

[ccyokes]

Ok, so how do you actually do that? The only two options under the drop down were first level or last level. There didn't appear to be a way to change the second level, that was the issue.

[Pramod.kadam]

Hi @ccyokes ,

For that, select the balloon with 1.22 and select 'last level' option to renumber 22 to other number.

Thanks,

[ccyokes]

As seen in the included screenshots though, there is no balloon with 1.22. That number refers to the group of components contained within it but has no body of its own to point to. All the bodies that a balloon could connect to are subcomponents of 1.22 such as 1.22.1 or 1.22.2

1.22 is simply the group containing for 1.22.1, 1.22.2, etc. and not its own thing. I've included links to the drawing and model file so you can see what I mean yourself and demonstrate what you mean if possible. The drawing has the roof currently listed as component 1.14 since I fixed it using the roundabout method this time. However, there is no component with only 1.14, they all have a third decimal position as all the bodies are in subcomponents of this.

https://a360.co/480Z9bU - model

https://a360.co/3V4YoqN - drawing

[bwalker145]

@Pramod.kadam  The bubbles for components used as sub-groups/sub-assemblies only appear if they're at the root level & the parts list is set to "First Level". The group bubbles disappear when changed to "All Level" (as it's now bubbling all individual components), not letting you adjust the numbering for 2nd/3rd/etc. tier components.

[ccyokes]

That's right. In my specific example it does seem to be smart enough to only show the second level components because all of the components are 1.something and there are no 2.something parts.

But that only works because I split 1 and 2 into separate drawings. In any other case it wouldn't help to renumber the parts before expanding to full level since you would either not see the second level when it's set to first level, or not be able to edit it when it's set to full level.

And let's just take a moment to appreciate how stellar the auto placement for bubbles is. I know trying to auto place those better probably isn't worth the dev time, but still.