-
-
Notifications
You must be signed in to change notification settings - Fork 595
Unable to save array of pointers in cloud code #434
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
can you provide the server logs when running with VERBOSE=1? |
verbose=1 throws huge log messages,
|
and what object is supposedly saves as a pointers array? I don't see any pointer arrays, but plain old objects. And nothing related to the code snipped you provided. |
Sorry for the wrong log, I've updated the previous log |
This is not an array of pointers, if I loot at a single element:
Also, it saves just fine. |
any extra information along with pointer like the one posted above makes it save as Create an array field |
is it an issue with the JS SDK or parse-server? AFAICT this seems to be on parse-server. Can you provide the verbose log for a fetch of that object? |
I think the issue seem to be with parse server, as I am not able to save the pointer details along with any other meta information even while saving from PHP. Should I post this issue under parse-server? |
Yes that would be better, please also fill completely the issue template from the parse-server issue report. |
Sure will do .. thanks |
var planobjar = []; for(var item of plansel) { var planob = {"objectId": item.planid, "__type": "Pointer", "className": "Plans"}; var pobj = {"planid": planob, "qty": item.qty, "unit":item.unit}; planobjar.push(planob); } var nClass = Parse.Object.extend("myClass"); var robj = new nClass(); robj.set ( 'planSelection', planobjar); robj.save({ success: function(planres) { // code }, error:function(error) { // code } });
If I try to save this array into an array field it doesn't save, but if it's an array without pointer it saves properly
The text was updated successfully, but these errors were encountered: