Here's what I think is going on:
Ext.data.Model is responsible for holding the proxy and field. Setting those properties on a store is discouraged in favor of MVC, though it was the only way before Ext-JS MVC came along.
A store always uses the proxy associated with the model object. When you pass in a fields
property to a store, an anonymous Model
is created with a default proxy. You shouldn't use that when specifying proxies. From the doc
For anything more complicated, such as specifying a particular id property or associations, a Ext.data.Model should be defined and specified for the model config.
My suggestion is that you create the models dynamically based on fields so you don't have any of the anonymous Model voodoo.
function createModelWithCustomProxy(fields) {
return Ext.define('FDG.store.reading.Mymodel' + Ext.id(), {
extend: 'Ext.data.Model',
fields: fields,
proxy: {
type: 'memory',
reader: {
type: 'json',
totalProperty: 'tc',
root: 'Result'
}
}
}
});
var fdgstore = Ext.create('Ext.data.Store', {
model: createModelWithCustomProxy(fields);
});
fdgstore.loadRawData(output);
this.reconfigure(fdgstore, columns);