-
Notifications
You must be signed in to change notification settings - Fork 140
[FIX] MRP BOM creation #109
base: 10.0
Are you sure you want to change the base?
[FIX] MRP BOM creation #109
Conversation
The configurator was creating a new BOM, every time a configuration was retrieved! Routine now only creates a BOM if there is none. Also, refactored to allow for overriding and hooks. This allows custom code to create a default BOM before the attributes are added, and for more clever adding of products (quantities, etc).
@PCatinean I will add some tests when you finish refactoring and I will re-propose the merge. |
Codecov Report
@@ Coverage Diff @@
## 10.0 #109 +/- ##
==========================================
+ Coverage 61.62% 62.21% +0.58%
==========================================
Files 14 14
Lines 1368 1392 +24
==========================================
+ Hits 843 866 +23
- Misses 525 526 +1
Continue to review full report at Codecov.
|
Any updates on this? |
Very interesting PR, any updates on this ? |
@elvise Not really - the branch is stable - I have it in 2 deployed environments, but unmerged here. |
The issue is fixed in v12 ? Do you have merged any others good features ? 😁 |
@elvise I have a lot of custom features for our main 2 clients who use this. However, both are on v10 and I have not at all looked at the 12 dev, and a long time since I was involved in 11. |
@richard-willdooit sounds good! |
@elvise EE, but there is nothing Enterprise dependent in the code. It is all backend (Sales Order) dependent code, as they are not using the configurator on the website, and they are not using it for Purchasing (they manufacture their configured products) |
@richard-willdooit in this PR its included also this: If yes I’m interesting complete this PR and make also porting for V12 |
It appears that the v11/v12 product_configurator_mrp module is non-functional, at least in terms of generating BOMs (as described in Issue #167). Can anyone verify this? |
hi there, any good news for this PR ? |
The configurator was creating a new BOM, every time
a configuration was retrieved! Routine now only
creates a BOM if there is none.
Also, refactored to allow for overriding and hooks.
This allows custom code to create a default BOM before
the attributes are added, and for more clever adding
of products (quantities, etc).