I have noticed a difference in how bom qty behaves in 2022, 2021 and 2020.
Please try the following in Inventor 2022:
In 2021 and 2020, REBUILD ALL was not necessary. The "rebuild" happened immediately. This has caused a big issue with one of our customers. (I haven't tested this in versions prior to 2020.) Has this behavior changed or am I misunderstanding something?
I have noticed a difference in how bom qty behaves in 2022, 2021 and 2020.
Please try the following in Inventor 2022:
In 2021 and 2020, REBUILD ALL was not necessary. The "rebuild" happened immediately. This has caused a big issue with one of our customers. (I haven't tested this in versions prior to 2020.) Has this behavior changed or am I misunderstanding something?
I checked this behaviour at my side, but it works like expected. So no rebuild needed in R2022.2. Do you have any additional rules running in templates? did you test it with the original templates as well?
I checked this behaviour at my side, but it works like expected. So no rebuild needed in R2022.2. Do you have any additional rules running in templates? did you test it with the original templates as well?
Can you confirm you didn't miss a step in my instructions? Is it possible you tested it in Inventor 2021 or a prior version?
Seems strange this behavior would be different on your workstation. This has been tested and confirmed on 4 different workstations on Inventor 2022 and 2022.2
Please see my attachments to make ensure we are talking "apples to apples".
Thanks
Can you confirm you didn't miss a step in my instructions? Is it possible you tested it in Inventor 2021 or a prior version?
Seems strange this behavior would be different on your workstation. This has been tested and confirmed on 4 different workstations on Inventor 2022 and 2022.2
Please see my attachments to make ensure we are talking "apples to apples".
Thanks
I double checked and yes there is an issue.
I checked the BOM on the model tab in the assembly and this one shows the correct / updated value of QTY. So that's why my previous reaction was "it's working fine". Because you showed me a parts list, I tested this as well and that's the place ware the problem comes up.
So the Model tab in the BOM shows the correct info, but QTY in the Structured and Partsonly view is not updated correctly. But the Unit QTY is updated correctly. QTY is the result of the ITEM QTY * Unit QTY
see the differences (900 mm was the previous length value in my sample):
I also checked if this also appears with a custom Mode state, but the problem remains. So I guess it's a bug.
I double checked and yes there is an issue.
I checked the BOM on the model tab in the assembly and this one shows the correct / updated value of QTY. So that's why my previous reaction was "it's working fine". Because you showed me a parts list, I tested this as well and that's the place ware the problem comes up.
So the Model tab in the BOM shows the correct info, but QTY in the Structured and Partsonly view is not updated correctly. But the Unit QTY is updated correctly. QTY is the result of the ITEM QTY * Unit QTY
see the differences (900 mm was the previous length value in my sample):
I also checked if this also appears with a custom Mode state, but the problem remains. So I guess it's a bug.
@johnsonshiue can you confirm this?
@johnsonshiue can you confirm this?
Apologies for the delay. I can confirm the reported behavior with the BOM table not showing the correct Qty. I have created a defect for us to investigate - INVGEN-59832. Thanks for reporting - the steps to reproduce were clear and awesome!!
We did rework BOM functionality in 2022 to accomodate model state workflows and its quite possible the behavior has changed. We will get back to you on our findings. In the meantime, as you pointed out, just do a rebuild ALL to get over the issue.
Thanks
-shiva
Apologies for the delay. I can confirm the reported behavior with the BOM table not showing the correct Qty. I have created a defect for us to investigate - INVGEN-59832. Thanks for reporting - the steps to reproduce were clear and awesome!!
We did rework BOM functionality in 2022 to accomodate model state workflows and its quite possible the behavior has changed. We will get back to you on our findings. In the meantime, as you pointed out, just do a rebuild ALL to get over the issue.
Thanks
-shiva
Can't find what you're looking for? Ask the community or share your knowledge.