Sage 100

Does anyone have any working samples of Work Order Release/Close (or other transaction entry types) import jobs that they wouldn't mind sharing? My imports appear to work as far as the VI Log is concerned but when I go to Transaction Entry, there is no batch and no transaction number. And there's very little on the KB to refer to. Any samples or thoughts would be appreciated! I'm also attaching one configuration of the job that I have been working with, in case someone sees something interesting. Thanks in advance!

What version? I have someone just upgraded to 2017 and i can't get the danged batch/transaction to show up no matter what, but if they choose to print and update all batches, it is there. Each time this client has upgraded over the years (luckily they don't upgrade each version), we've had to redo the WO imports because they stop working.

I'm working in 2015 right now. What version did they just come from?

BTW - I could see the imported data in the transaction tables too and I just tested updating the Register, and my Release did update, so my issue is the exact same as your client's, Beth. How do they fix it every upgrade?

Well, we haven't GOT a fix for this one. Previously, we switched between using the import specifically for Misc Labor (which is what their import is for) and the general import for any WO transaction. This time, I've tried both and it's not working no matter what. I think once I created the batch number manually and then created the Transaction number manually, got out and back in, and it was there, but even that I can't get to work consistently. So as of right now, they're updating everything when they do this, which works for them because the guy who does labor and payroll is a part-timer who logs in remotely in the evenings.

I just haven't had time to make a fuss yet...

Thank you, Beth. I'll see how they want me to proceed on this. I will most likely report it to Sage and see if Scott Brady will look at it. I'll post a resolution if I get one.

I don't have a VI import that I have done for WO, however, here are a couple of tips that have helped me. * Arrange the VI fields on the Data tab as the same order the Available fields list. * Add the new batch in the data entry window then set the BATCH_NUMBER in the VI import job to prompt so the user will enter the batch number when running the import. * Setup a new import job

for one client, we had to add ""Perform Only"" on the Detail Record tab of a VI job, I think so that the sort files got updated. For another client, we were importing a close transaction and we had to add Perform Logic for the WO.TXCLOS (see screen shot attached)

@BethBowers Paul Chen got the Release working for me (my Close worked correctly from the beginning to create and see the batch and imported record). He added Perform Logic for Record Type 1 to the ""Release"" record type on the Records tab (see attached).

Thanks, @AmberPrayfrock - I'll try this at my client's.