There's are suggestion for the MOD Squad - Add a check box selection option on Tab ONE of a VI import to SKIP the first line of the import file!!! Can't add up the number of times I have to delete the header line of imports before importing. Yes, record selection works, but how much easier it could be to add the check box option......
------------------------------
Jeff Schwenk
FORMER 90M Board Member -140,000,000 is a TERRIBLE thing to waste!!!
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------
Original Message:
Sent: 09-23-2021 17:38
From: Barbara Goldstein
Subject: VI import into IM_TransactionHeader - transaction date
Yes @David Overholt, that's what I meant to communicate. That's what I did. I'll test out @Kevin Moyes theory about line feeds next. Thanks!
------------------------------
Barbara Goldstein
Sr. Consultant
DSD Business Systems
San Jose CA
800.627.9032 x221
------------------------------
Original Message:
Sent: 09-23-2021 15:51
From: David Overholt
Subject: VI import into IM_TransactionHeader - transaction date
I'm not sure what you mean by selection criteria, do you mean a conditional on the first column? That won't skip the first line. Instead go to Tab #4 and double click on Skip Record and set it to skip the value in field #1 in my screen shot below I'm skipping if the first column has "NAME" as the first 4 characters (be sure to set the length appropriately – it defaults to a length of 1 character.
Original Message:
Sent: 9/23/2021 3:04:00 PM
From: Barbara Goldstein
Subject: RE: VI import into IM_TransactionHeader - transaction date
@David Overholt, yes, batches are turned on. With your suggestion, I found a Sage KB that describe how to configure the batch number field (i.e. make it "Assign" and leave everything else blank). The import now succeeds. One thing I noticed is that it is creating failed header records because it's reading the column headers in Row 1. I thought if I put in a selection criterion for the first text in cell A1, it would skip the whole row, but it isn't doing that.
------------------------------
Barbara Goldstein
Sr. Consultant
DSD Business Systems
San Jose CA
800.627.9032 x221
Original Message:
Sent: 09-23-2021 08:29
From: David Overholt
Subject: VI import into IM_TransactionHeader - transaction date
Are batches turned on? The message invalid header will happen if batches are turned on and you are not assigning a batch number
Original Message:
Sent: 9/23/2021 8:17:00 AM
From: alan niergarth
Subject: RE: VI import into IM_TransactionHeader - transaction date
Have you tried the YYYYMMDD format as a runtime assign?
------------------------------
alan niergarth
Velosio LLC