Array reader screws up when fields have custom convert fn's

1. 
   

   Thank you for reporting this bug. We will make it our priority to review this report.

   
   


2. 
   
   
   

   
   

   
   

   Array reader screws up when fields have custom convert fn's

   
   

   
   

   Array reader screws up when fields have custom convert fn's

   
   
   
   

   
   

   Steps:
   
   (1) Create a model with a set of fields and proxy with an array reader.
   
   (2) Add a convert function to one of the fields which is returned from the server (any field but the last)
   
   (3) Load the record
   

   What is expected:
   
   The Array reader matches record columns returned from the server to fields on the model, based on the order the fields are defined within the model's config. 1st column -> 1st field, 2nd column -> 2nd field, etc.

   
   

   What happens instead:
   
   Fields without a convert fn are hoisted above fields with a convert fn, and this order of fields is then used to map record columns to fields. So data is set on the wrong columns.

   
   

   
   

   
   

   
   

   
   

   
   
   
   

   ---

Array reader screws up when fields have custom convert fn's