-
19 Jun 2012 12:50 AM #11
This still isn't fixed in 4.1, please make it happen, I think it's an important issue, there are cases where you don't want to use Readers.
-
19 Nov 2012 3:40 PM #12
Any updates?
Any updates?
I too was just bit by this bug.
I am populating certain stores in my app via store.loadData() instead of via individual store readers because I am fetching data for several related stores in a single Ajax request. So I don't want/need the proxy/reader config baked into the store.
These stores DO have fully defined model classes, and those models have an ID property ({name:'id', type:'int'}. And of course the data being loaded as an ID property as well. But after the call to loadData() the resulting records have auto-generated IDs, which means I can't refer to them reliably using my consistent / known primary keys.
Any updates? The workaround posted didn't seem to apply to 4.1, or I didn't understand it.
-
26 Nov 2012 8:35 AM #13
This is being fixed for 4.2
Search the forum: http://www.google.com/coop/cse?cx=01...%3Az7of1ufqccu
Read the docs too: http://extjs.com/deploy/dev/docs/
Scope: http://extjs.com/forum/showthread.ph...642#post257642
You found a bug! We've classified it as
EXTJSIV-3455
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote