Sage 100

Why does **VI** say an item code is ""not on file""? The client has about 5 item codes that regularly get rejected by VI saying the item code is not on file. I thought it was because they had a quote mark in the item code (I did NOT teach them that). So I tested one and renumbered it, removing the quote mark. It still says item code not on file! I've tried csv, XLSX, tab delimited. They all say not on file. I notice there are other item codes with a quote mark that import fine. Any suggestions where to look next?

Is there a space before the first char in either the input file or in Sage?

Good call. But I checked again and there's no leading space.

Copy to a new Item Code and retest. What happens?

Already did the renumber utility and got rid of the "". No change, which was strange

What are they importing into?

It happens when importing to every file so far, ci item, I'm transaction entry, vendor item alias...

Hey Clark - On 2 occasions I've been asked to set up Item Maintenance to strip spaces and all unprintable ASCII characters as the Item Code is copy/pasted in. The clients were creating new items by copying them from a website or a selecting text from a PDF and then pasting them into Item Maint. Of course both common and weird characters would appear before and after the item code. In your case with VI we can accomplish exactly the same with straightforward Perform Logic that would _cleanse_ the incoming Item Code from the import file. But for now, you could try this if you choose: 1- Create a Temp field as string and choose Assign Temp on Key Assigns. Replace it from the column with your item code. 2- For ItemCode set Operation = Calculated then use this Calculation Expression to get rid of common troublemakers. It doesn't cover all characters you might run across but has common ones I've seen that interfere (LF, CR, dbl quote, single quote, pct sign, question mark, hashtag). Also I'm stripping spaces before and after but not in between (NOTE that Mas actually allows spaces before like Beth was mentioning and in between). `STP(SUB(SUB(SUB(SUB(SUB(SUB(SUB(Temp001$,$0A$,""""),$0D$,""""),CHR(34),""""),CHR(39),""""),CHR(37),""""),CHR(63),""""),CHR(35),""""),2,"" "")`

I'd use DFDM to take a look. Invisible characters might be shown as spaces. Most commonly for us a user will copy / paste from Excel, and trailing invisible characters come along for the ride.

The issue that puzzles me is that I used the inventory Delete/Change utility to change the item number from CASTER-4""-SWV to CASTER-4-SWV. I got rid of the "" quote mark I thought was causing the problem. But when I did a new import test with the new part number (no ""), it still gave the msg ""item code not on file"". Changing the item number should have cleared out any extraneous characters. This leads me to believe there is another issue going on other than the item number itself. Especially when other item numbers with quotes ("") in them do import with no issue. Curiouser and Curiouser...

In the renumber utility did you type out the new ItemCode manually? Or just delete the quote (which won't necessarily remove invisible characters)?

Along the lines of what Kevin said, it sounds like the source item number in the import file still has extra characters. I'll send you a Chat.

I typed in the number manually

I manually typed the item number in the source file too. But I'll check my work when I get back to it. Right now juggling two other projects :)

Rebuild key / sort files? Perhaps there is a bad index somewhere causing a false error.

Were all files selected on the Delete/Change Utility? It may be an associated file that's causing the issue.

Rebuild sort files.