Sage 100

VI to SO Entry Header, updating some UDFs. Getting failed records msg that I must provide a valid credit card authorization number. These S/O's have a credit card payment type, but have not been authorized yet. They don't authorize until they get ready to ship. Attached is a snip of the VI message. Where's a good dog when you need one?

I suspect it's one of the other cc-related fields, like PayBalance, etc. How about the AuthorizationRequiredFlag? And I wouldn't know about any good dogs - none live here. (We're sitting a screaming pitbull today and my nerves are shot. If he wasn't so darned cute...)

It turns out it was that the credit card authorization field needed to have a value in it in the S/O Application. If it was blank, I couldn't even save the existing Sales Order. The issue was that I had copied data from the live company to the test company (90 minutes thanks to Sage Exchange) The live company is credit card enabled, the test company is not. The import problem was in the test company. When I did a small test in the live company, the VI Job worked fine. Morals to learn: 1. Credit Card processing introduces another layer of variables that can make testing in a test company more complex. 2. VI issues sometimes only reflect a problem in the actual software process, not the import job. 3. COMPUTERS.... never mind.

Computers - hate 'em, don't you?

I love computers, it's lazy programmers I can't stand...