Question on order fields defaulting from customer record (2 replies)
Randy, I believe I understand your question.
IMan processes all of its data in batches, so all orders in one specific instance of an integration will get processed one transform at a time.
http://www.realisable.co.uk/support/documentation/IManUG/DataConcepts/DataFlow.htm
If you have several orders being processed and they are updating the same customer record each order's data will overwrite the customer record. The last order will make the last update to the customer and such when the order is created the customer's details will be copied to each of the orders.
Our recommendation would be to place a filter prior to the customer update and filter any data for the generic customer to prevent the update of the generic customer record.
Then in the order import simply set all the details (it's all available) as you would have for the customer.
Thanks
Closed due to inactivity.
Hey guys, not sure if this is the correct spot in the forum or not. If not, apologies.
We had a client point out a possible timing problem with the current sample order import, and could use a little advice. In this case, they realized that for guest orders (or other orders which will import under, and insert/create, 1 specific Sage Customer), it's possible for the Customer record to be overwritten before the order import takes place. Any fields which are not explicitly mapped on the order could possible default to incorrect data in the customer record.
Have you guys heard of any instances of this happening from other users?
This may be more of a Sage question, but is there a list of fields which we know default to the customer record if not explicitly mapped? This will allow us to map every field to ensure no incorrect data is pulled from the Customer record.
Thanks.