I migrated a customer from iman 4.2 to a new server with iman 5.1 PU9. I had 2 issues - the first is that smtp email and email group test successfully but when you go into a step in a job that sends out more than one emails - by document # for example - it blows up with bad email address. (Same error occurs if you schedule the job.) This I had to request the hot fix for - it will be included in a future release, per Iman support.

The second issue I found was that when posting orders to Sage 300 where the line item had an optional field value mapped, AND there was a misc charge line - the order would not post when set to Reject Record. When set to Abort, you would get a very generic error: invalid procedure call or argument.

Ultimately, what we found is that I had set the value of the optionial field to " " or "" for the misc charge - because in Sage 300, misc charges don't actually have opt fields, but you have to do something with it, since the field must be mapped for the line item details. Iman 4.2 recognized that the opt field didn't exist for misc charges and properly posted the order. Iman 5.1 PU9 blew it up.

Iman support helped me resolve the issue by setting the value for the misc charge to NULL. The formula was called ZZWEBLINEID and the formula for the misc charge aggregate was: SetFieldNull("ZZWEBLINEID")  -- this allowed me to map an actual value for the line item opt field, but set it to null for the misc charge. Genius!