-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 I was wondering how the features of a product variant make it into the order/invoice if they are not saved within the product name? Scenario: Customer buys variant 1 with Features "red" and "XXL". There are plenty of methods to show them on the product detail page or in the cart - e.g.: ProductWorker.getVariantDistinguishingFeatures(product) ProductWorker.getProductFeaturesByApplTypeId(product, 'STANDARD_FEATURE') But they cannot be used for the order/invoice as variants can change (e.g.: entity ProductFeatureAppl) but the invoice should not change. So is the feature info already stored somewhere else for the order/invoice or how to do so? Cheers, René - -- René Scheibe * [hidden email] TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterföhring Geschäftsführer: Henrik Klagges, Gerhard Müller, Christoph Stock Sitz: Unterföhring * Amtsgericht München * HRB 135082 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAky5hccACgkQUXs9EHvIuCr9UACdHZPP/qq+mAPkhN61QIX4//11 kaEAn2RuAezflfnpk/YM9s5siqDeXR9q =4Ezp -----END PGP SIGNATURE----- |
if I remember right the orderItem has an relationship to the feature.
you can pull the data from that into the invioceitem.Itemdescription ========================= BJ Freeman Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=52> Specialtymarket.com <http://www.specialtymarket.com/> Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Rene Scheibe sent the following on 10/16/2010 4:00 AM: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I was wondering how the features of a product variant make it into > the order/invoice if they are not saved within the product name? > > Scenario: > Customer buys variant 1 with Features "red" and "XXL". > There are plenty of methods to show them on the product detail page > or in the cart - e.g.: > > ProductWorker.getVariantDistinguishingFeatures(product) > ProductWorker.getProductFeaturesByApplTypeId(product, 'STANDARD_FEATURE') > > But they cannot be used for the order/invoice as variants can change > (e.g.: entity ProductFeatureAppl) but the invoice should not change. > > So is the feature info already stored somewhere else for the order/invoice > or how to do so? > > Cheers, > René > - -- > René Scheibe * [hidden email] > TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterföhring > Geschäftsführer: Henrik Klagges, Gerhard Müller, Christoph Stock > Sitz: Unterföhring * Amtsgericht München * HRB 135082 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAky5hccACgkQUXs9EHvIuCr9UACdHZPP/qq+mAPkhN61QIX4//11 > kaEAn2RuAezflfnpk/YM9s5siqDeXR9q > =4Ezp > -----END PGP SIGNATURE----- > |
In reply to this post by Rene Scheibe
Hi List,
it seems that information about the product variant that has been selected by the customer when ordering is never persisted at the invoice or the order. Are we missing something here or is this a bug/unimplemented? Has anyone has ever used variant products and can provide some insight on this issue? Thanks, greetings, - Karl On 16.10.2010, at 13:00, Rene Scheibe wrote: > I was wondering how the features of a product variant make it into > the order/invoice if they are not saved within the product name? > > Scenario: > Customer buys variant 1 with Features "red" and "XXL". > There are plenty of methods to show them on the product detail page > or in the cart - e.g.: > > ProductWorker.getVariantDistinguishingFeatures(product) > ProductWorker.getProductFeaturesByApplTypeId(product, 'STANDARD_FEATURE') > > But they cannot be used for the order/invoice as variants can change > (e.g.: entity ProductFeatureAppl) but the invoice should not change. > > So is the feature info already stored somewhere else for the order/invoice > or how to do so? |
Free forum by Nabble | Edit this page |