Sage 100

Error 41 VI_ImportJobCompile.pvc I upgraded a client from v 2016 to 2018 Client reported getting an error 55 while running a VI job. I went in to recompile it and when compiling I got an Error 41 in VI_ImporJobCompile.pvc. I thought the job was corrupted so I rebuilt it line by line and kept saving it while rebuilding it. This was a fairly involved VI job, but everything saved fine until I got to the records tab where I have logic to skip the record if field #4 in the source file is blank. It looks like this is a new feature in 2018 that I can't leave the field VALUE blank on the skip record properties. I use it all the time in VI to skip lines with no value. For now I took that skip record command out and I'll tell the client to watch for failed records where before they would be skipped. Anyone seen this? or have a workaround?

YIKES! I use that all the time! What is you actually type in a space in the Value field?

I use the select tab to skip but you probably aren't importing that field??

I wouldn't panic just yet, I cannot reproduce this on my stock installation. but I can reproduce it on their install with a new import job. - might be something related to 3rd party modifications (they have a lot of work order/Scanco enhancements).

try using the Less Than option with a value of 0.

Error 41's can come from invalid fields which exist in a table-lookup (like transaction codes, item-type codes). Also from invalid dates.

@DavidSpeckII - That worked!! thank you @LeeGraham that makes sense. Since I have a workaround I'll probably not dig much deeper. I'll say that I created a few dummy import jobs into different modules and tables. I always get the error if I have a blank value in that skip logic. It doesn't happen on my local install with PU1. Their install is PU2 but I'm leaning towards (hoping) it is something unique to this client and third party enhancements.

one other thing to add: this happens while compiling the import job; immediately after hitting the ACCEPT button in import job maintenance. We never get to the point of trying to run the job.

Did the ""Less Than 0"" skip records correctly like the previous ""Equal blank"" criteria in the prior version?

Yes, the less than zero did work; but I know that the source file data would have Alpha characters in that field on any record that I'm not skipping. I'm not sure if some special characters might get through but since I know the source data well enough, that will work for this import.