Sage 100

Received this e-mail a few minutes ago. Dear Jeffrey, Please note that the issue reported on Case 4566680 from our friends at Bottomline Software, Inc. has been resolved. The fix has been made available in the latest product update PU6 for v 4.40. Didn't remember which one it was so I looked it up. I had reported it a year ago (8/3/10) regarding the inability to renumber IM items via VI imports in V4.4, which was related to an issue with VI imports to the delete, renumber, merge utility that I reported during beta of v4.4 in December, 2009. Should I test it???????????????

Well, I would certainly like to know. I have a customer that this affects. Also, with the way Sage has been going, it's a good idea to test it yourself before telling the customer it's fixed, then putting in the fix, and it either doesn't fix it or fixes it and breaks something else.

From the Release notes of PU 6. The files are back. Visual IntegratorNew in Product Update 4.40.0.6Visual Integrator Import Job IM_DeleteChangeItems now imports successfully without error.1DE 95653 PER 110408 Resolution ID 527467

John, did you actually test this. This was fixed in PU 2 also....................

This morning I received a survey covering this case inquirying how well support did in resolving the issue. Let's see, only took 19 months to ultimately resolve. At least the support person was pleasant......

A couple days ago, I just checked to see if I could set one up. The IM_DeleteChangeItems file was available again and allowed data to be setup. I didn't take the time to test. My client wanted to delete a bunch of items and due to 4.4's attitude about history and item deletions, we feel importing to the new inactive flag in CI_Item is the most effective way to get them what the want.