Sage 100

4.40 SO Invoice Import - have to import the same lines twice because they contain both an item number and a restock fee (sometimes). After the 2nd import, the NONTAXABLE totals only contain what was imported a second time. Am I missing something, or do I have to do some fricking perform logic to get the totals to be correct? I don't recall it being this difficult in prior versions.

Is the nontaxable total an import field? It may need to be a cumulative amount in the import file.

Hell, no - not anymore. TaxableAmount and NonTaxableAmount are not available any more. Because Sage knows best how to figure those amounts...

When you say same lines are are you running a second import using the same source lines creating new lines on the invoice or are you using the line key and importing over the existing lines?

New lines on the invoice. There are 2 fields in the same line in the import file that translate into 2 separate lines in the actual invoice.

You could use a union query to seperate the items into their own lines and do one import.

Thats my thought too. I was going to ask what your source file was. I'd probably run it through a script and split the lines out.

Sounds like a bug in the existing perform logic so Dan's/Brett's suggestion should work around it.

The beauty of a union query is that there are no extra steps. It just works - kind of like a filter. V/I sees the data through the query which is interpreted with software built into Windows (MDAC) and no other software is required.

Tell me more, because you be talking jibberish right now... :-)

One can use MS Access or SQL to build a query file (""Select * From YourimportCSV where <record 1 criteria> Union All Select * from YourImportCSV where <record 2 criteria>"" Order by <invoice/line>) to which you direct V/I. V/I will see two records (an item and a restock fee) for every one. I recommend MS Access because you don't have to have it or anyother software installed. You can create the file off site.

I think the social cast iPod app lost my last post. Oh well. Sweet solution Dan. I tend to fall back to my coding roots. I'd just use a script to open the file, write out the necessary extra lines and then use the script to run the import while I was at it.

Dan - INteresting..... off to play around and see what damage I can do...

Oh, the power of Access queries. VERY handy tools!!!