-
10 Apr 2012 9:52 PM #1
store.sync doesn't work properly
store.sync doesn't work properly
it stops to synchronize after having "idProperty: 'not_id'" in the model. It means either store.sync has bug or you need to remove idProperty from model's config and tell the people the only id which proxy understands is 'id'.
-
11 Apr 2012 5:45 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 34,107
- Vote Rating
- 453
Is this using the localstorage proxy?
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
11 Apr 2012 6:07 AM #3
-
11 Apr 2012 6:12 AM #4Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 34,107
- Vote Rating
- 453
There is already an open bug about (internally submitted by myself) for syncing when you define your own id.
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
11 Apr 2012 6:14 AM #5
-
11 Apr 2012 6:18 AM #6Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 34,107
- Vote Rating
- 453
It's marked to be but still open.
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
11 Apr 2012 6:19 AM #7Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 34,107
- Vote Rating
- 453
Just posting the ticket number for reference: TOUCH-2666
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
12 Apr 2012 1:57 PM #8
As a work around to anyone else having this problem.
Code:recordItem = store.add({ id: 1, data: "this is the data" })[0]; recordItem.phantom = true; store.sync();
-
7 May 2012 9:59 PM #9
This code has a problem.
This code has a problem.
jlwarren1, unfortunately this code causes a problem.
If you add a record to the local storage like your code, the local storage will change the record's id.
Code:recordItem = store.add({ id: 5, data: "this is the data" })[0]; recordItem.phantom = true; store.sync(); console.debug("record id: ' + recordItem.getId()); // record id : 1
-
11 Jun 2013 1:37 AM #10
Is this still open more than a year later!?!?!?! I'm having the exact same problem, and I can't believe it's not fixed yet.
You found a bug! We've classified it as
TOUCH-2666
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote