[2.1] Inconsistent assignment of 'internalId' on models when using store.add()

[mankz]

When calling add on a store, things go wrong.

Ext.define('M', {
    extend : 'Ext.data.Model',
    config : {
        idProperty : 'foo',
        fields : ['foo']
    }
});

var store = new Ext.data.Store({ model : 'M', data : [{ foo : 5 }] })
console.log(store.first().internalId);        // => 5
store.add([{ foo : 1 }]);
console.log(store.last().internalId);        // undefined

[mitchellsimoens]

Thanks for the report! I have opened a bug in our bug tracker.

[mankz]

Bump, any news on this one? Breaking a few things for us...

Related thread in our forum http://bryntum.com/forum/viewtopic.p...p=18207#p18207

[camdagr8]

Any news on this? I'm trying to insert an item to a store after removing an item. It appears to display correctly in a list but when you click an item in the list, it's returning a record w/o accounting for the inserted or removed records.

[camdagr8]

For a very hackish work around, I ended up creating 2 stores and when I update or remove items from the main store, I do a removeAll() on it and loop through the 2nd store and add it's values to the main store, this seems like the only way to get a fresh internal id for each item.

[mankz]

Bump, any idea when this might get fixed?

[mankz]

Bump bump bump, 3 months...

[TommyMaintz]

Somehow this bug got into the backlog in our system and we have only just dug this one up. This will be fixed in 2.2.1. Sorry for the delay