Is it possible to modify the delimiter in multi-level BOMs? By default the delimiter is a period we need it to be a hyphen.
The Item numbers update automatically. You can modify them to some extend and control how BOM changes propagate in the drawing. But none are a stellar option.
I can see this working if you have small assemblies or need this to work in limited applications. But as a standard BOM & drawing setting this is a no-no. Only and only if you have good pressing reasons I would proceed down that road.
The drawbacks are vast...Merely consider the space requirements. Your balloons would grow way to big on anything 2 or more levels deep. That by itself will cause issues if you automate the process. Any stacked balloon would inevitable shift due to the size change. And that's just the beginning.
The only way I know of is to use API and traverse all balloons and replace the "." with "-". That however will be static text and break the parametric link to the BOM. If your BOM changes, you would need to run a routine that sets the balloon back to default values, then runs the conversion procedure again.
I would not recommend messing with the BOM live update functionality.
Thanks for the quick reply. What we really need is the balloons to have the hyphen. I know the Balloon text comes from the BOM. So im guessing we would be in the same boat?
Interestingly enough, the "separator" (as shown in the Options picture below) only applies to dimensions.
I know that it says that, but I expected it to apply to all numbers. But it doesn't.
It doesn't affect the Bill Of Material (if you have a column with numbers [like a weight column]).
It also doesn't affect the detailed item number.
I know this doesn't help, it was just surprising to discover.
Thanks Dan. This is interesting, i have never messed with that setting.
The only way I know of to do this while keeping the balloons linked to the table would be to assign that designation as a custom property, and call out that property in the table and balloons instead of the default numbering. I'm not recommending it, because I can foresee some issues with setting it up and keeping them consecutive, but it should work if you can't find a better method and just absolutely have to have the dash instead of the period.
Ya, im actually sending out a internal survey to see if anyone actually cares one way or another. My preference is to move to periods...buuuttt, if there's a elegant way to accomplish this, i'm all game.
The drawbacks are definitely vast, thanks for all the input Elmar.
Retrieving data ...