I think a lot of people, myself included need a BOM table which will display user defined balloon numbers. I don't want the index numbers in the balloons. Ideally, I need a table that I can have the BOM plus a column in which I can define the balloon number required. This would save a lot of time from having to manually create balloon notes with my desired number. Thx
Solved! Go to Solution.
Fix index is definitely the fastest, easiest method. If I was doing it regularly, I would make a set of mapkeys to get me most of the way there.
The component parameter method I mentioned would be way more upfront work and would be much less user friendly (more training).
If you want your suggestion to be voted on post in the first link below. The ideas were searched with the following results:
Found one for balloon numbers instead of dimensions for quality/checking:
Fixing indices numbers.
Or post your idea in the first link.
I would use a component parameter and set that in your repeat region bom instead of the index.
You would need to make a custom bom balloon to use that instead of the index number.
Search for component parameters bom index or something similar.
It's completely do-able
I'm curious as to why simply using a repeat region box, then FIXING the index numbers to what you want doesn't work for you. You realize you can re-order the indexes of your BOM to have any part be any number, and it locks it that way, right? For reference, you should always fix your repeat region anyway to keep the index numbers from changing and messing up note references to them.
We are concerned that a component parameter makes you check out that part, then assign it a specific item number and that number would have to be the same every time. This wouldn't work for us because that part may have a different item number each time. Plus, if you have a big enough BOM, checking out all those parts would suck.
whoops, I guess I replied to the wrong message. That was meant for the reply above. Anyway, for the unfixing - fixing of the index numbers this works but is a little cumbersome and difficult to use especially if you don't understand repeat regions. I suppose my only gripe is hard to use.
Thanks for the reply.
Explain your rational as to why a custom BOM number is preferred over a system generated number that is propagated to related items automatically?
Fixing the BOM table locks the numbers so they don't change, unless you unfix the table and resort it. Even then, BOM numbers will update, but item numbers in a note will not.
Specifically a "component parameter" is only in the assembly and is assigned to that component within that assembly. It is not a part parameter which exists in the part.
If you are of the opinion that fixing the index is cumbersome, then using component parameters would be a much higher level of cumbersome and would require much more work and much more effort but it would provide much more flexibility.
Did you know you can not only lock the items individually (assigning whatever numbers you want to each), or lock the entire region at a time (to whatever numbers are currently show)? If you simply MUST have part "A" as index 1, and part "B" as index 2, then, yes, you have to assign them one-by-one. I don't find it tedious, how ELSE would you do it one-by-one?