How to rebuild corrupt BOM tables

[Mike Gera]

Is there a way to rebuild a "corrupt" BOM table?

Today, for example, I had a BOM table that had two item #6's in it. Everything else on the drawing and in the BOM table (aside from the double 6-row) was in order. All settings and such were correct.

(FWIW, both item #6 balloons displayed as "6")

A CTRL-Q did not correct the issue.

Ultimately, I had to delete the BOM table and then recreated it to fix the problem.

Is there a better way to force a full rebuild of a BOM table?

Thanks.

[Hansjoerg]

Check this Setting:

Dokument Settings -> Table -> BOM

[AlexLachance]

Is there a way to rebuild a "corrupt" BOM table?

Today, for example, I had a BOM table that had two item #6's in it. Everything else on the drawing and in the BOM table (aside from the double 6-row) was in order. All settings and such were correct.

(FWIW, both item #6 balloons displayed as "6")

A CTRL-Q did not correct the issue.

Ultimately, I had to delete the BOM table and then recreated it to fix the problem.

Is there a better way to force a full rebuild of a BOM table?

Thanks.

We get that issue and haven't figured out a solution. We always end up deleting and recreating the BOM and it can be a pain for us because the times it does occur is on our electric, hydraulic and pneumatic drawings and those have special numberings which need an ordering.

If you figure something out, let me know!

[Mike Gera]

Check this Setting:

Dokument Settings -> Table -> BOM
2023-03-02 10_30_54-Window.png

"Automatic Update of BOM" was already checked.

[Mike Gera]

We get that issue and haven't figured out a solution. We always end up deleting and recreating the BOM and it can be a pain for us because the times it does occur is on our electric, hydraulic and pneumatic drawings and those have special numberings which need an ordering.

If you figure something out, let me know!

Ugh, so it is a bug. What a drag.

OK, thanks for the intel.

[AlexLachance]

Ugh, so it is a bug. What a drag.

OK, thanks for the intel.

I'm on 2019 SP5, maybe the bug has been adressed since.

[SPerman]

I'm on 2019 SP5, maybe the bug has been adressed since.

FIFY

[Hansjoerg]

I am also on SWX 2019 SP 5. And i have no problems with the BOM

[AlexLachance]

I am also on SWX 2019 SP 5. And i have no problems with the BOM

It happens for us in very specific cases. Also, all our "projects" are done from existing projects, so basically a drawing can be new but the drawing that was used to create it could date back to 2013.

[Mike Gera]

It's a shame that DS doesn't like, you know, fix the bug.

[SPerman]

I have had it happen to me in 2022, but like Alex, many of my files are "Save As" from older drawings, which probably has template implications.

[jcapriotti]

Is there a way to rebuild a "corrupt" BOM table?

Today, for example, I had a BOM table that had two item #6's in it. Everything else on the drawing and in the BOM table (aside from the double 6-row) was in order. All settings and such were correct.

(FWIW, both item #6 balloons displayed as "6")

A CTRL-Q did not correct the issue.

Ultimately, I had to delete the BOM table and then recreated it to fix the problem.

Is there a better way to force a full rebuild of a BOM table?

Thanks.

Can you show your BOM properties in the property manager? Also, was this after an upgrade or the same version?

[mp3-250]

we are on pdm and the boms can become very messed up if the whole assembly tree is not rebuilt from the bottom to the top.
if you have some "dirt" sub assembly that was set as read only rebuilding from the top is not going to work as rebuilding the leaf would trigger its parents to rebuild and so on.
we run in even more problems-bugs with cutlists where even deleting and inserting again won't solve the problem(s).
at this point we have such a collection of critical issues that I wonder if ds really debug and test their software seriously.

[Mike Gera]

we are on pdm and the boms can become very messed up if the whole assembly tree is not rebuilt from the bottom to the top.
if you have some "dirt" sub assembly that was set as read only rebuilding from the top is not going to work as rebuilding the leaf would trigger its parents to rebuild and so on.
we run in even more problems-bugs with cutlists where even deleting and inserting again won't solve the problem(s).
at this point we have such a collection of critical issues that I wonder if ds really debug and test their software seriously.

My perception is that DS is controlled by its marketing department. Programmers and engineers have no say whatsoever in how things are run.

[SPerman]

I wonder if ds really debug and test their software seriously.

Welcome to 2023, where "agile" programming means "the customer will find the bugs for us."

[mp3-250]

when I finish to deploy the admin image for the company upgrade I think I will have a lot to talk about here... too much material for a single post.

OT closed

[CarrieIves]

This is a late reply, but I have accidently overwritten the BOM item number before. (I think I did something with the BOM balloon to change the number accidently.) It's hard to figure out that is what happened. Double check that you don't have anything overwritten in the BOM.