I’ve been testing simple configurators that model different aspects of what we actually want to do in production. First I created a single-level configurator that uses component pricing and updates material quantities on the quote BOM. The configured part receives correct price based on the configurator inputs and material prices. So far so good!
For my next experiment, I created a similar configurable part with component pricing, and a parent part containing two of the configurable part. When the parent is configured, the subassembly configurator runs twice and the resulting BOM is correct. But the component pricing does not reflect the BOM. If the two subassemblies are configured differently, then instead of the sum of the prices, the parent receives two times the price of the first one.
The document rule in the subassembly configurator is just
Pricing.QuotePrice = Pricing.ComponentPricing;
I also tried
Pricing.QuotePrice += Pricing.ComponentPricing;
Has anyone else run into this? I don’t see any related PRBs…