phantomIdField for AjaxStore
Posted: Thu Jul 11, 2019 1:54 am
Hi,
While using the ajaxstore, for newly added items the store sets a string based phantomId but into the id field itself.
If we set the id field before the object is added to null, it causes an unhandled promise rejection after the response from the server is received.
Setting the ids to -1 seem to work without any issues.
I have two related questions:
1) Is it possible to disable phantomId generation or set it in a different field like we can in Schedule's crud manager?
2) If we cannot do anything in (1) or if they're not planned is it ok initialising ids to -1? Will we have any consequences down the road?
Br,
Kaan.
While using the ajaxstore, for newly added items the store sets a string based phantomId but into the id field itself.
If we set the id field before the object is added to null, it causes an unhandled promise rejection after the response from the server is received.
Setting the ids to -1 seem to work without any issues.
I have two related questions:
1) Is it possible to disable phantomId generation or set it in a different field like we can in Schedule's crud manager?
2) If we cannot do anything in (1) or if they're not planned is it ok initialising ids to -1? Will we have any consequences down the road?
Br,
Kaan.