In a test upgrade of a client's database from 4.40 to 10.6, there seems to be an issue with the Dues Importer failing on large imports (31,000+ payments). The process is failing around the 16,376 to 16,383 trans count.
Looking at a SQL trace, I can see that the update to the Batch record is malformed. It says "...LAST_UPDATED = WHERE ...".
In this case it should have said "...LAST_UPDATED =''MANAGER'' WHERE ...".
Pretty dang [more colorful adjective deleted to preserve G rating] annoying to have the thing fail for something that matters so little!
Submitted as SMR #126552. Will update when I get ASI's response.
UPDATE #2: As of 5/10/06, ASI rates this issue as Urgent. They already have a fix for this -- I tested a new build of the imisar.lbr and my test file of 31K+ payments did not fail. And it seems to be importing faster! Tech Support says .05 will be released within two weeks and I assume it will be sooner. Yahoo!
UPDATE: As of 5/5/06, ASI confirms that it is an issue and Dev has already provided Tech Support with a new build to test. I don't know when it will be available. I hope it makes it into the soon-to-be-released .04 patch.