Yeah, seems like decoding the data on load is the best option after all.

Specifying 'fields' config in either the store or within the reader seems to work initially, but the way the extended json reader works is if there is meta data passed in along with the data, then the initial configs get overwritten and I could not for the world of me figure out how to cancel such an overwrite...