The original idea, if I'm not wrong was this:
a) add a "store" method to the ProductConfigWrapper (or Worker) to store
the configuration in the ProductConfigConfig entity (by assigning a new
configId)
b) add a new constructor to the ProductConfigWrapper to load a wrapper
from a stored configId
Jacopo
Jacopo Cappellato wrote:
Hans,
the best way to go is to probably implement the part of the configurable
stuff that was originally planned but then never completed: add support
for storing the configurations.
There are already entities for this in the system (for details, please
search on the mailing lists because I've posted there 2-3 times details
about the original plans - try searching for ProductConfig* or
ProductConfigConfig that is the entity that should store the
configurations)
Then the config id could be added to the quote (but we should discuss a
bit more about this, I guess, because is a pretty major change),
request, order items etc...
Or (probably better) we could use the configId to create a new special
type of variant product (something like "variant configuration",
associated to the configurable product template and to the given
configId) and then use the new productId in quotes, requests, order
items etc...
Jacopo
Hans Bakker wrote:
Can please somebody help me find the best solution?
I need to put a configurable product on a quote. and later convert the
quote into an order.
The problem here is that only the total price of the configuration can
be stored in the quote but not the parts it consist out of and the
quantity.
In the order it is solved by creating a productionrun and connecting
the required products and quantities there. In the cart it is stored
in the configWrapper.
The only way i see now is to create a new table for the quoteItem and
probably for the shopping list and the CustRequestItem too..... to
store the product and quantity.....
anybody any suggestions?
thanks in advance,
regards,
Hans
