We have a situation where a customer uses an "Accounts Payable" template containing several dynamic fields for GL Codes.  The table that this data is pulled from contains 7 columns and about 300 rows.

For each record that they scan, they may need to enter as many as 20-25 different financial transactions.  In a perfect world, there would be a way to have a multi-value collection of fields, but that functionality doesn't exist, so instead they have 25 iterations of each field on them template ('GLFund01' - 'GLFund25', 'GLDepartment01' - 'GLDepartment25', and so on).  I've attached a screenshot showing a section of the template.

Unfortunately, this is causing a SERIOUS lag when opening the scanning window.  It takes over 3 minutes for the scanning window to load, because it has to load all of these dynamic fields.  Even if I only include only 10 iterations of each field, it still takes over a minute for the Scanning window to load.

I've tried the MaxDropDownLength and CacheFieldValues attributes, as per KB Article 1013198, but that hasn't helped.  Obviously, we'd rather just use multi-value fields, rather than 25 iterations of each field, but that isn't going to work without some sort of field "collections".  

I know this feature has been requested in the past?  Is this on the horizon at all?  If not, is there any other way for us to speed up the loading process in Scanning?  The lag only seems to exist when loading the Scanning window.  If I import a document, there is no lag at all when I have it defaulting to the Accounts Payable.