Hi Forrest,
I'd suggest to use OrderAttribute to store custom data for the order.
Regards,
Michael Brohl
ecomify GmbH
www.ecomify.de
Am 18.06.15 um 16:30 schrieb Forrest Rae:
Hans, thanks for the reply.
I do agree with you that invoice is a better place for this data, I
can change the entit
Hans, thanks for the reply.
I do agree with you that invoice is a better place for this data, I can
change the entity I'm extending. Still, I would like to capture this
data at order entry, and I'm wondering about best way to do that given
the design of the order entry process. It's my under
Isn't the invoice you want follow up for payment?
Regards,
Hans
On 18/06/15 12:38, Forrest Rae wrote:
Hi Everyone,
I'm wondering about best practices here, and want to avoid going down a
route that might lead to pain and suffering.
I need to track three custom pieces of data per sales order.
Hi Everyone,
I'm wondering about best practices here, and want to avoid going down a
route that might lead to pain and suffering.
I need to track three custom pieces of data per sales order. This data
is used for contacting the customer for payment. One piece of data is a
purchase order number,
