We have a job in which we make frequent use of the Maximum and Minimum functions to populate a parent record with the largest or smallest value of a string from the child records. When upgrading from IMan v4 to IMan v5 (product update 10) this job failed because these functions now only work for numeric fields.  This seems to be consistent with the use of Maximum and Minimum functions in VB, and different from the Max and Min functions in some other contexts, such as MS SQL.

I don't know whether this is built into IMan 5, or is a side effect of a specific version of another program or feature being used on the same server. Has this been encountered before?  Is there an alternative function within IMan?  (We considered various sorting options, and ended up collecting these Max and Min values in the sql dbreader).

Example: in a hierarchy with InvoiceHeader and InvoiceDetail, if we want to record the alphabetically largest item number on an invoice, we would use a formula at the invoice header level, Maximum("ITEMNO", "InvoiceDetail").  In v4 this works.  In v5 this gives us an error ""Error occurred in transform [Map].  Error - Error whilst evaluating expression on for field [maxItem] on transaction [InvoiceHeader]. Error - Type mismatch: Error in function [Maximum]. The value [A11030] could not be converted to [number]. at Line [1] Position [0]"