Sage 100

Have a client with one main vendor.  I'm trying to create an import which will use a spreadsheet they have that has all of the items on it and they just put a qty next to the one they are buying this time.
I've assigned the vendor in the file, and did a NEXT for the Order Number and pointed it to a field that will be blank, since I only want it to get a new number on the first record.

It's creating a new PO for each item.

SO, I added the PO Header Comment field and also pointed IT to a blank field, using REPLACE, so that I had at least one field in the header that wasn't assign.  It won't import the header AT ALL if I do that - both lines come up with an error that say no valid header.

Looking buggy to me, or else I've missed some other new hoop we have to jump through to get these to work.  Help!

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN
------------------------------

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------

Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN
------------------------------

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772
------------------------------

Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------

Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772
------------------------------


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772
------------------------------

Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

Sucks to be us.  @Michelle Taylor​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------

Original Message:
Sent: 01-08-2020 11:28
From: Michelle Taylor
Subject: Importing POs in 2019

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772
------------------------------


Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

Thought i had a post either on here or Sage City regarding some recent findings about NEXT and it requiring at least one header field using the Replace operand with valid data (can't be blank) because of the way VI Imports save off the last value read from the source, but only for fields with the Replace operand and this compiled string of last values is compared against the next values read from the source. So either put something in the source that will be the same for every record read or use some perform logic on the after read event to slip a value into a bogus column variable using the variable IMP$[X] where X is the column number that you are sure won't be used in the actual source file, then point your field that you want to use the replace operand on to that bogus column number. I think the OrderDate would be a good field to use if you plan on always using the current system date for the POs created by the import anyway. Just use something like the following (the exclamation point is part of the code, tells VI to EXECUTE instead of PERFORM the code).
IMP$[10]=coSession'SystemDate$ !

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 01-08-2020 11:31
From: Beth Bowers
Subject: Importing POs in 2019

Sucks to be us.  @Michelle Taylor​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------


Original Message:
Sent: 01-08-2020 11:28
From: Michelle Taylor
Subject: Importing POs in 2019

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

@David Speck II - I do have a Replace - the Header Comment field, pointing to a blank field.  Or the Email field, pointing to a blank field.  I've tried several, and this is what I've done with SO imports before and the Next works fine that way.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------

Original Message:
Sent: 01-09-2020 04:02
From: David Speck II
Subject: Importing POs in 2019

Thought i had a post either on here or Sage City regarding some recent findings about NEXT and it requiring at least one header field using the Replace operand with valid data (can't be blank) because of the way VI Imports save off the last value read from the source, but only for fields with the Replace operand and this compiled string of last values is compared against the next values read from the source. So either put something in the source that will be the same for every record read or use some perform logic on the after read event to slip a value into a bogus column variable using the variable IMP$[X] where X is the column number that you are sure won't be used in the actual source file, then point your field that you want to use the replace operand on to that bogus column number. I think the OrderDate would be a good field to use if you plan on always using the current system date for the POs created by the import anyway. Just use something like the following (the exclamation point is part of the code, tells VI to EXECUTE instead of PERFORM the code).
IMP$[10]=coSession'SystemDate$ !

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 01-08-2020 11:31
From: Beth Bowers
Subject: Importing POs in 2019

Sucks to be us.  @Michelle Taylor​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:28
From: Michelle Taylor
Subject: Importing POs in 2019

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

But do you have any other header fields with the Replace operand or are they all assigned or calculated?
If you only have the one Replace field and it is always pointing to a blank column for every record, i believe that is the issue, I have not gotten a chance to prove this 100% but it seems similar to some VI import issues i was running into a month or so ago that had to doing with the Next operand.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 01-09-2020 07:57
From: Beth Bowers
Subject: Importing POs in 2019

@David Speck II - I do have a Replace - the Header Comment field, pointing to a blank field.  Or the Email field, pointing to a blank field.  I've tried several, and this is what I've done with SO imports before and the Next works fine that way.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------


Original Message:
Sent: 01-09-2020 04:02
From: David Speck II
Subject: Importing POs in 2019

Thought i had a post either on here or Sage City regarding some recent findings about NEXT and it requiring at least one header field using the Replace operand with valid data (can't be blank) because of the way VI Imports save off the last value read from the source, but only for fields with the Replace operand and this compiled string of last values is compared against the next values read from the source. So either put something in the source that will be the same for every record read or use some perform logic on the after read event to slip a value into a bogus column variable using the variable IMP$[X] where X is the column number that you are sure won't be used in the actual source file, then point your field that you want to use the replace operand on to that bogus column number. I think the OrderDate would be a good field to use if you plan on always using the current system date for the POs created by the import anyway. Just use something like the following (the exclamation point is part of the code, tells VI to EXECUTE instead of PERFORM the code).
IMP$[10]=coSession'SystemDate$ !

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-08-2020 11:31
From: Beth Bowers
Subject: Importing POs in 2019

Sucks to be us.  @Michelle Taylor​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:28
From: Michelle Taylor
Subject: Importing POs in 2019

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

OK, I'll add a column containing a "1" and try that...  Otherwise, no dice, because everything on the spreadsheet needs to be the same order.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------

Original Message:
Sent: 01-09-2020 10:07
From: David Speck II
Subject: Importing POs in 2019

But do you have any other header fields with the Replace operand or are they all assigned or calculated?
If you only have the one Replace field and it is always pointing to a blank column for every record, i believe that is the issue, I have not gotten a chance to prove this 100% but it seems similar to some VI import issues i was running into a month or so ago that had to doing with the Next operand.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 01-09-2020 07:57
From: Beth Bowers
Subject: Importing POs in 2019

@David Speck II - I do have a Replace - the Header Comment field, pointing to a blank field.  Or the Email field, pointing to a blank field.  I've tried several, and this is what I've done with SO imports before and the Next works fine that way.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 04:02
From: David Speck II
Subject: Importing POs in 2019

Thought i had a post either on here or Sage City regarding some recent findings about NEXT and it requiring at least one header field using the Replace operand with valid data (can't be blank) because of the way VI Imports save off the last value read from the source, but only for fields with the Replace operand and this compiled string of last values is compared against the next values read from the source. So either put something in the source that will be the same for every record read or use some perform logic on the after read event to slip a value into a bogus column variable using the variable IMP$[X] where X is the column number that you are sure won't be used in the actual source file, then point your field that you want to use the replace operand on to that bogus column number. I think the OrderDate would be a good field to use if you plan on always using the current system date for the POs created by the import anyway. Just use something like the following (the exclamation point is part of the code, tells VI to EXECUTE instead of PERFORM the code).
IMP$[10]=coSession'SystemDate$ !

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-08-2020 11:31
From: Beth Bowers
Subject: Importing POs in 2019

Sucks to be us.  @Michelle Taylor​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:28
From: Michelle Taylor
Subject: Importing POs in 2019

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

Woo hoo, @David Speck II!  I added a column with "1"s all the way down, but then had to add a Shipto Code  of 1 to the Shipto file so I had something valid to read that 1 into (I didn't want it to be in the comment).  THAT WORKED.  THANK YOU!!!!!!!!!!!!​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------

Original Message:
Sent: 01-09-2020 10:07
From: David Speck II
Subject: Importing POs in 2019

But do you have any other header fields with the Replace operand or are they all assigned or calculated?
If you only have the one Replace field and it is always pointing to a blank column for every record, i believe that is the issue, I have not gotten a chance to prove this 100% but it seems similar to some VI import issues i was running into a month or so ago that had to doing with the Next operand.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 01-09-2020 07:57
From: Beth Bowers
Subject: Importing POs in 2019

@David Speck II - I do have a Replace - the Header Comment field, pointing to a blank field.  Or the Email field, pointing to a blank field.  I've tried several, and this is what I've done with SO imports before and the Next works fine that way.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 04:02
From: David Speck II
Subject: Importing POs in 2019

Thought i had a post either on here or Sage City regarding some recent findings about NEXT and it requiring at least one header field using the Replace operand with valid data (can't be blank) because of the way VI Imports save off the last value read from the source, but only for fields with the Replace operand and this compiled string of last values is compared against the next values read from the source. So either put something in the source that will be the same for every record read or use some perform logic on the after read event to slip a value into a bogus column variable using the variable IMP$[X] where X is the column number that you are sure won't be used in the actual source file, then point your field that you want to use the replace operand on to that bogus column number. I think the OrderDate would be a good field to use if you plan on always using the current system date for the POs created by the import anyway. Just use something like the following (the exclamation point is part of the code, tells VI to EXECUTE instead of PERFORM the code).
IMP$[10]=coSession'SystemDate$ !

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-08-2020 11:31
From: Beth Bowers
Subject: Importing POs in 2019

Sucks to be us.  @Michelle Taylor​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:28
From: Michelle Taylor
Subject: Importing POs in 2019

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

Did you consider using the after read perform logic to set the system date into a column that you could point the order date to?

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 01-09-2020 19:40
From: Beth Bowers
Subject: Importing POs in 2019

Woo hoo, @David Speck II!  I added a column with "1"s all the way down, but then had to add a Shipto Code  of 1 to the Shipto file so I had something valid to read that 1 into (I didn't want it to be in the comment).  THAT WORKED.  THANK YOU!!!!!!!!!!!!​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------


Original Message:
Sent: 01-09-2020 10:07
From: David Speck II
Subject: Importing POs in 2019

But do you have any other header fields with the Replace operand or are they all assigned or calculated?
If you only have the one Replace field and it is always pointing to a blank column for every record, i believe that is the issue, I have not gotten a chance to prove this 100% but it seems similar to some VI import issues i was running into a month or so ago that had to doing with the Next operand.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-09-2020 07:57
From: Beth Bowers
Subject: Importing POs in 2019

@David Speck II - I do have a Replace - the Header Comment field, pointing to a blank field.  Or the Email field, pointing to a blank field.  I've tried several, and this is what I've done with SO imports before and the Next works fine that way.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 04:02
From: David Speck II
Subject: Importing POs in 2019

Thought i had a post either on here or Sage City regarding some recent findings about NEXT and it requiring at least one header field using the Replace operand with valid data (can't be blank) because of the way VI Imports save off the last value read from the source, but only for fields with the Replace operand and this compiled string of last values is compared against the next values read from the source. So either put something in the source that will be the same for every record read or use some perform logic on the after read event to slip a value into a bogus column variable using the variable IMP$[X] where X is the column number that you are sure won't be used in the actual source file, then point your field that you want to use the replace operand on to that bogus column number. I think the OrderDate would be a good field to use if you plan on always using the current system date for the POs created by the import anyway. Just use something like the following (the exclamation point is part of the code, tells VI to EXECUTE instead of PERFORM the code).
IMP$[10]=coSession'SystemDate$ !

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-08-2020 11:31
From: Beth Bowers
Subject: Importing POs in 2019

Sucks to be us.  @Michelle Taylor​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:28
From: Michelle Taylor
Subject: Importing POs in 2019

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

You crack me up.  @David Speck II​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------

Original Message:
Sent: 01-09-2020 19:43
From: David Speck II
Subject: Importing POs in 2019

Did you consider using the after read perform logic to set the system date into a column that you could point the order date to?

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 01-09-2020 19:40
From: Beth Bowers
Subject: Importing POs in 2019

Woo hoo, @David Speck II!  I added a column with "1"s all the way down, but then had to add a Shipto Code  of 1 to the Shipto file so I had something valid to read that 1 into (I didn't want it to be in the comment).  THAT WORKED.  THANK YOU!!!!!!!!!!!!​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 10:07
From: David Speck II
Subject: Importing POs in 2019

But do you have any other header fields with the Replace operand or are they all assigned or calculated?
If you only have the one Replace field and it is always pointing to a blank column for every record, i believe that is the issue, I have not gotten a chance to prove this 100% but it seems similar to some VI import issues i was running into a month or so ago that had to doing with the Next operand.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-09-2020 07:57
From: Beth Bowers
Subject: Importing POs in 2019

@David Speck II - I do have a Replace - the Header Comment field, pointing to a blank field.  Or the Email field, pointing to a blank field.  I've tried several, and this is what I've done with SO imports before and the Next works fine that way.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 04:02
From: David Speck II
Subject: Importing POs in 2019

Thought i had a post either on here or Sage City regarding some recent findings about NEXT and it requiring at least one header field using the Replace operand with valid data (can't be blank) because of the way VI Imports save off the last value read from the source, but only for fields with the Replace operand and this compiled string of last values is compared against the next values read from the source. So either put something in the source that will be the same for every record read or use some perform logic on the after read event to slip a value into a bogus column variable using the variable IMP$[X] where X is the column number that you are sure won't be used in the actual source file, then point your field that you want to use the replace operand on to that bogus column number. I think the OrderDate would be a good field to use if you plan on always using the current system date for the POs created by the import anyway. Just use something like the following (the exclamation point is part of the code, tells VI to EXECUTE instead of PERFORM the code).
IMP$[10]=coSession'SystemDate$ !

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-08-2020 11:31
From: Beth Bowers
Subject: Importing POs in 2019

Sucks to be us.  @Michelle Taylor​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:28
From: Michelle Taylor
Subject: Importing POs in 2019

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

Importing into a Temp field might be good enough.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 01-09-2020 20:18
From: Beth Bowers
Subject: Importing POs in 2019

You crack me up.  @David Speck II​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------


Original Message:
Sent: 01-09-2020 19:43
From: David Speck II
Subject: Importing POs in 2019

Did you consider using the after read perform logic to set the system date into a column that you could point the order date to?

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-09-2020 19:40
From: Beth Bowers
Subject: Importing POs in 2019

Woo hoo, @David Speck II!  I added a column with "1"s all the way down, but then had to add a Shipto Code  of 1 to the Shipto file so I had something valid to read that 1 into (I didn't want it to be in the comment).  THAT WORKED.  THANK YOU!!!!!!!!!!!!​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 10:07
From: David Speck II
Subject: Importing POs in 2019

But do you have any other header fields with the Replace operand or are they all assigned or calculated?
If you only have the one Replace field and it is always pointing to a blank column for every record, i believe that is the issue, I have not gotten a chance to prove this 100% but it seems similar to some VI import issues i was running into a month or so ago that had to doing with the Next operand.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-09-2020 07:57
From: Beth Bowers
Subject: Importing POs in 2019

@David Speck II - I do have a Replace - the Header Comment field, pointing to a blank field.  Or the Email field, pointing to a blank field.  I've tried several, and this is what I've done with SO imports before and the Next works fine that way.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 04:02
From: David Speck II
Subject: Importing POs in 2019

Thought i had a post either on here or Sage City regarding some recent findings about NEXT and it requiring at least one header field using the Replace operand with valid data (can't be blank) because of the way VI Imports save off the last value read from the source, but only for fields with the Replace operand and this compiled string of last values is compared against the next values read from the source. So either put something in the source that will be the same for every record read or use some perform logic on the after read event to slip a value into a bogus column variable using the variable IMP$[X] where X is the column number that you are sure won't be used in the actual source file, then point your field that you want to use the replace operand on to that bogus column number. I think the OrderDate would be a good field to use if you plan on always using the current system date for the POs created by the import anyway. Just use something like the following (the exclamation point is part of the code, tells VI to EXECUTE instead of PERFORM the code).
IMP$[10]=coSession'SystemDate$ !

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-08-2020 11:31
From: Beth Bowers
Subject: Importing POs in 2019

Sucks to be us.  @Michelle Taylor​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:28
From: Michelle Taylor
Subject: Importing POs in 2019

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

Yeah, I should expand on that - yes, doing that scripting is certainly a possibility.  If I tried to do it, there would be 12 hours of my life wasted, along with my elevated blood pressure.  I could ask someone else to do it, but then I'm wasting someone else's time on something that, in this case, can be fixed more crudely.

@David Speck II - I know that if YOU were fixing it, it would take you 2 seconds and it would be beautiful, though.  :-)​  I am in awe of your programming, even after "all" these years.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------

Original Message:
Sent: 01-10-2020 11:30
From: Kevin Moyes
Subject: Importing POs in 2019

Importing into a Temp field might be good enough.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 01-09-2020 20:18
From: Beth Bowers
Subject: Importing POs in 2019

You crack me up.  @David Speck II​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 19:43
From: David Speck II
Subject: Importing POs in 2019

Did you consider using the after read perform logic to set the system date into a column that you could point the order date to?

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-09-2020 19:40
From: Beth Bowers
Subject: Importing POs in 2019

Woo hoo, @David Speck II!  I added a column with "1"s all the way down, but then had to add a Shipto Code  of 1 to the Shipto file so I had something valid to read that 1 into (I didn't want it to be in the comment).  THAT WORKED.  THANK YOU!!!!!!!!!!!!​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 10:07
From: David Speck II
Subject: Importing POs in 2019

But do you have any other header fields with the Replace operand or are they all assigned or calculated?
If you only have the one Replace field and it is always pointing to a blank column for every record, i believe that is the issue, I have not gotten a chance to prove this 100% but it seems similar to some VI import issues i was running into a month or so ago that had to doing with the Next operand.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-09-2020 07:57
From: Beth Bowers
Subject: Importing POs in 2019

@David Speck II - I do have a Replace - the Header Comment field, pointing to a blank field.  Or the Email field, pointing to a blank field.  I've tried several, and this is what I've done with SO imports before and the Next works fine that way.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 04:02
From: David Speck II
Subject: Importing POs in 2019

Thought i had a post either on here or Sage City regarding some recent findings about NEXT and it requiring at least one header field using the Replace operand with valid data (can't be blank) because of the way VI Imports save off the last value read from the source, but only for fields with the Replace operand and this compiled string of last values is compared against the next values read from the source. So either put something in the source that will be the same for every record read or use some perform logic on the after read event to slip a value into a bogus column variable using the variable IMP$[X] where X is the column number that you are sure won't be used in the actual source file, then point your field that you want to use the replace operand on to that bogus column number. I think the OrderDate would be a good field to use if you plan on always using the current system date for the POs created by the import anyway. Just use something like the following (the exclamation point is part of the code, tells VI to EXECUTE instead of PERFORM the code).
IMP$[10]=coSession'SystemDate$ !

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-08-2020 11:31
From: Beth Bowers
Subject: Importing POs in 2019

Sucks to be us.  @Michelle Taylor​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:28
From: Michelle Taylor
Subject: Importing POs in 2019

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

That may work as long as the temp field uses the Replace operation, is assigned on the header, and points to a column that is not blank but is consistent for the lines to all be assigned to the same header.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 01-10-2020 11:30
From: Kevin Moyes
Subject: Importing POs in 2019

Importing into a Temp field might be good enough.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 01-09-2020 20:18
From: Beth Bowers
Subject: Importing POs in 2019

You crack me up.  @David Speck II​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 19:43
From: David Speck II
Subject: Importing POs in 2019

Did you consider using the after read perform logic to set the system date into a column that you could point the order date to?

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-09-2020 19:40
From: Beth Bowers
Subject: Importing POs in 2019

Woo hoo, @David Speck II!  I added a column with "1"s all the way down, but then had to add a Shipto Code  of 1 to the Shipto file so I had something valid to read that 1 into (I didn't want it to be in the comment).  THAT WORKED.  THANK YOU!!!!!!!!!!!!​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 10:07
From: David Speck II
Subject: Importing POs in 2019

But do you have any other header fields with the Replace operand or are they all assigned or calculated?
If you only have the one Replace field and it is always pointing to a blank column for every record, i believe that is the issue, I have not gotten a chance to prove this 100% but it seems similar to some VI import issues i was running into a month or so ago that had to doing with the Next operand.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-09-2020 07:57
From: Beth Bowers
Subject: Importing POs in 2019

@David Speck II - I do have a Replace - the Header Comment field, pointing to a blank field.  Or the Email field, pointing to a blank field.  I've tried several, and this is what I've done with SO imports before and the Next works fine that way.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 04:02
From: David Speck II
Subject: Importing POs in 2019

Thought i had a post either on here or Sage City regarding some recent findings about NEXT and it requiring at least one header field using the Replace operand with valid data (can't be blank) because of the way VI Imports save off the last value read from the source, but only for fields with the Replace operand and this compiled string of last values is compared against the next values read from the source. So either put something in the source that will be the same for every record read or use some perform logic on the after read event to slip a value into a bogus column variable using the variable IMP$[X] where X is the column number that you are sure won't be used in the actual source file, then point your field that you want to use the replace operand on to that bogus column number. I think the OrderDate would be a good field to use if you plan on always using the current system date for the POs created by the import anyway. Just use something like the following (the exclamation point is part of the code, tells VI to EXECUTE instead of PERFORM the code).
IMP$[10]=coSession'SystemDate$ !

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-08-2020 11:31
From: Beth Bowers
Subject: Importing POs in 2019

Sucks to be us.  @Michelle Taylor​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:28
From: Michelle Taylor
Subject: Importing POs in 2019

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN

Exactly... I've done that before, but each business object is it's own beast.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 01-10-2020 11:39
From: David Speck II
Subject: Importing POs in 2019

That may work as long as the temp field uses the Replace operation, is assigned on the header, and points to a column that is not blank but is consistent for the lines to all be assigned to the same header.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 01-10-2020 11:30
From: Kevin Moyes
Subject: Importing POs in 2019

Importing into a Temp field might be good enough.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 01-09-2020 20:18
From: Beth Bowers
Subject: Importing POs in 2019

You crack me up.  @David Speck II​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 19:43
From: David Speck II
Subject: Importing POs in 2019

Did you consider using the after read perform logic to set the system date into a column that you could point the order date to?

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-09-2020 19:40
From: Beth Bowers
Subject: Importing POs in 2019

Woo hoo, @David Speck II!  I added a column with "1"s all the way down, but then had to add a Shipto Code  of 1 to the Shipto file so I had something valid to read that 1 into (I didn't want it to be in the comment).  THAT WORKED.  THANK YOU!!!!!!!!!!!!​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 10:07
From: David Speck II
Subject: Importing POs in 2019

But do you have any other header fields with the Replace operand or are they all assigned or calculated?
If you only have the one Replace field and it is always pointing to a blank column for every record, i believe that is the issue, I have not gotten a chance to prove this 100% but it seems similar to some VI import issues i was running into a month or so ago that had to doing with the Next operand.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-09-2020 07:57
From: Beth Bowers
Subject: Importing POs in 2019

@David Speck II - I do have a Replace - the Header Comment field, pointing to a blank field.  Or the Email field, pointing to a blank field.  I've tried several, and this is what I've done with SO imports before and the Next works fine that way.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-09-2020 04:02
From: David Speck II
Subject: Importing POs in 2019

Thought i had a post either on here or Sage City regarding some recent findings about NEXT and it requiring at least one header field using the Replace operand with valid data (can't be blank) because of the way VI Imports save off the last value read from the source, but only for fields with the Replace operand and this compiled string of last values is compared against the next values read from the source. So either put something in the source that will be the same for every record read or use some perform logic on the after read event to slip a value into a bogus column variable using the variable IMP$[X] where X is the column number that you are sure won't be used in the actual source file, then point your field that you want to use the replace operand on to that bogus column number. I think the OrderDate would be a good field to use if you plan on always using the current system date for the POs created by the import anyway. Just use something like the following (the exclamation point is part of the code, tells VI to EXECUTE instead of PERFORM the code).
IMP$[10]=coSession'SystemDate$ !

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-08-2020 11:31
From: Beth Bowers
Subject: Importing POs in 2019

Sucks to be us.  @Michelle Taylor​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:28
From: Michelle Taylor
Subject: Importing POs in 2019

I'm getting the same results as you, Beth.  The import works with assigns on the header and PO Date as Runtime, yet when I add in the Comment it won't import.

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 11:21
From: Beth Bowers
Subject: Importing POs in 2019

No, I don't.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-08-2020 11:17
From: Michelle Taylor
Subject: Importing POs in 2019

@Beth Bowers Do you have Header  ​Separate From Line Record selected?

------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772


Original Message:
Sent: 01-08-2020 07:42
From: Beth Bowers
Subject: Importing POs in 2019

@Nancy Hanson - I already have mine working this way (client inputs the PO#), but I want the Next to work as it's supposed to, so that they don't have to input the PO number.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625


Original Message:
Sent: 01-07-2020 18:14
From: Nancy Hanson
Subject: Importing POs in 2019

Hi  Beth
Attached is a VI job I use for importing PO's.  This customer inputs the PO# though but it does do 1 PO for the full spreadsheet.  I did a quick scan of the job and I have a Line Key in my file, could that be your missing piece?​  This job is in v2017.

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN