If I recall correctly from a recent VI job I worked on, the L.LineKey field will only be set if you use the Replace operation, which is disappointing because I was trying to do a calculation on it.
Here's a simple source.
The target order.
There are a couple ways around this, either perform logic or a temp field set to the Calculated operation that instead calls the EditLine method using whatever value you want to pass to the GetEditKey method.
The temp field must be before the L.* fields.
The results.
------------------------------
David Speck II
Tennessee Software Solutions
------------------------------
Original Message:
Sent: 11-25-2019 16:54
From: Kevin Moyes
Subject: VI Sales Order Import to Existing Line Key
Sorry... two L fields should be LineKey and what you are updating. Example:
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------
Original Message:
Sent: 11-25-2019 16:22
From: Kimberly Davis
Subject: VI Sales Order Import to Existing Line Key
I don't know what you mean. Can you explain? How do I put the sales order number in the lines?
------------------------------
Kimberly Davis
Lehman Wesley & Associates
Original Message:
Sent: 11-25-2019 15:10
From: Kevin Moyes
Subject: VI Sales Order Import to Existing Line Key
H field points to the SO# with the first two L. fields as SO# and the line key (zero padded)?
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON