ParseObject attributes of the ParseObject in afterSave/beforeSave triggers aren't valid for using in queries. #2000

Activity

1. zingano commented on Jun 9, 2016

   

   zingano

   on Jun 9, 2016

   More actions

   I think I am seeing something related but a different error - I'm getting {"code":119,"message":"Permission denied for this action."}

   I have an Account, which has an owning Customer. In the afterSave I want to update the count of Accounts in the Customer and add the Account to the Customer's array of Accounts.

   My afterSave for Account is:

   Parse.Cloud.afterSave("Account", function(request) {
   
       //Parse.Cloud.useMasterKey();
   
       console.log("request.object id " + request.object.id);
       if (request.object.existed()) {
           console.log("account existed, returning");
           return;
       }
   
       var sessionToken = request.user.getSessionToken()
       console.log("request.user.getSessionToken " + sessionToken);
   
       var customer = request.object.get("customer");
       console.log("pre-fetch got customer id " + customer.id);
   
       return customer.fetch({useMasterKey: true},{sessionToken: sessionToken}).then(function(customer) {
   
         console.log("got customer id " + customer.id);
           console.log("got customer " + customer.name);
           console.log("customer number of accounts - " + customer.numberOfAccounts);
           customer.increment('numberOfAccounts',1);
           customer.addUnique("accountsArray",request.object);
           return customer.save({useMasterKey: true},{sessionToken: sessionToken});
   
       }).then(function() {
           console.log("afterSave account SUCCESS");
   
       },function(error) {
           console.log("afterSave Account: FAIL" + JSON.stringify(error));
           logger.log("afterSave Account: FAIL" + JSON.stringify(error));
       });
   });

   The logs for these show at even after fetching, the Customer name and numberOfAccounts are undefined.

   2016-06-09T07:24:55.670083+00:00 app[web.1]: request.user.getSessionToken r:61f25908638952b2662929c29781626f
   2016-06-09T07:24:55.669723+00:00 app[web.1]: request.object id zcysCk91lo
   2016-06-09T07:24:55.670155+00:00 app[web.1]: pre-fetch got customer id uJfLlc1cnK
   2016-06-09T07:24:55.697868+00:00 app[web.1]: customer number of accounts - undefined
   2016-06-09T07:24:55.697207+00:00 app[web.1]: got customer id uJfLlc1cnK
   2016-06-09T07:24:55.697833+00:00 app[web.1]: got customer undefined
   2016-06-09T07:24:55.767929+00:00 app[web.1]: afterSave Account:    FAIL{"code":119,"message":"Permission denied for this action."}
   

   Both Customer and Account are only accessible to a role called Admin. The calling user (me) is a member of that Role.

   👍React with 👍1Reacted by DaveS
2. zingano commented on Jun 9, 2016

   

   zingano

   on Jun 9, 2016

   More actions

   In my code above, rather than fetching the Customer, I've tried doing a query like this: query.equalTo("objectId", customer.id);

   The Customer that is returned is in the same state as above - members are undefined.
3. zingano commented on Jun 9, 2016

   

   zingano

   on Jun 9, 2016

   More actions

   After doing some debugging in the Parse Server code that's returning my error, I think I'm getting that permissions fail because that class doesn't have "addField" permission. However, this code is not adding a field - I suspect Parse Server thinks that because the object is improperly fetched and its fields are undefined.
4. hramos commented on Jul 27, 2016

   

   hramos

   on Jul 27, 2016

   Contributor

   More actions

   We're closing this issue due to inactivity.

   If this is a bug you care about that is not getting attention, consider opening a pull request with a fix.

   👎React with 👎2Reacted by John Turnham and Tucker Chapin

   😕React with 😕2Reacted by Mattia Iavarone and Li3ro
5. hramos

   closed this as completedon Jul 27, 2016
6. zingano commented on Jul 28, 2016

   

   zingano

   on Jul 28, 2016

   More actions

   But the inactivity's from your side! In that case surely it should stay open?

   😄React with 😄2Reacted by Mattia Iavarone and John Turnham

   😕React with 😕3Reacted by Terry Xu, Diego and Tucker Chapin
7. shankslouis commented on Dec 8, 2016

   

   shankslouis

   on Dec 8, 2016

   More actions

   @zingano did you solve the ParseError 119? thrown in your afterSave function?