Sage 100

MAS 200 v. 4.5 sp 2 - Selecting ""test"" on a VI import may cause it to hang if there are any failed records. No message is listed and you can't ""cancel"". You end up having force an exit, shut down all remaining tasks, log back into MAS and then look at the VI log to see what the issue is. Executing/running the job, rather than testing, correctly logs any failures without hanging. Tres annoyning.

yes, and as we've learned recently, running as a test can change things in the live database such as the paid today field in AR open invoice file.

Also, importing into the Bill of Materials crashes, and if you have a 4.5 and a 4.4 on the same system, it then stops working in your 4.4, as well. Whee.

Geez - changing existing data when a VI runs in ""test""? Guess that's not a ""test"" if it's touching data. Beth what version 90/200? Workstation or on the server?

Moira - the original issue was with 4.50. But when I then tried it back on the 4.40 that was on the same server (and I'm pretty sure I was doing this via RDP), it no longer worked in the 4.40. I ended up having to cart the files back to my machine and import there.

A few years ago when the framework first came out and they still had sessions on VI it was explained to NOT do test imports in VI on any module in the Framework as you would get unpredictable results. To do imports in a backup company first and just accept.

Concur it's unpredictable. It's about the particular business object you are trying to import into and how VI (un)friendly it is. Recently devised way to import into Shipping Data Entry with combination of perform logic and scripts. Spent more time troubleshooting undesirable results with Test button than coding. In the end I put in perform logic to show a message that Test button is not supported on this import.