Why is `set` not working with `pipelines`?

Moralis General
#1

I’m certain I’m missing something obvious, but I can’t get set to work in a pipeline query:

const pipeline = [
    {
      project: {
        name: 1,
        audit: 1,
        totalScore: "unset",
      },
    },
    { set: { totalScore: "custom_value" } },
    { limit: maxFind },
  ];

I simply receive Invalid parameter for query: set. FYI, I did get addFields to work, but still curious. :thinking:

#2

Did you learn this set usage anywhere (same with addFields)? You may need to set that totalScore (on all objects?) afterwards.

#3

Saw set was an updated alias for addFields in the MongoDB docs. Was just curious why it didn’t work. Still using addFields for the time being as that appears to work.

#4

It could come from parse server, there is a limited list of allowed operations even if mongo db could support more depending on the version of mongodb.