Populate nested array in mongoose

Question

How can I populate  components  in the example document              v   1        id    5252875356f64d6d28000001        pages                        v   1            id    5252875a56f64d6d28000002            page                components                  525287a01877a68528000001                                            author    Book Author        title    Book Title        This is my JS where I get document by Mongoose     Project findById id  populate  pages   exec function err  project        res json project

User · Answer

I struggled with this for a whole bloody day. None of the solutions above worked. The only thing that worked in my case for an example like the following:

{
  outerProp1: {
    nestedProp1: [
      { prop1: x, prop2: y, prop3: ObjectId("....")},
      ...
    ],
    nestedProp2: [
      { prop1: x, prop2: y, prop3: ObjectId("....")},
      ...
    ]
  },
  ...
}

is to do the following: (Assuming populating after fetch - but also works when calling populate from the Model class (followed by exec))

await doc.populate({
  path: 'outerProp1.nestedProp1.prop3'
}).execPopulate()

// doc is now populated

In other words, the outermost path property has to contain the full path. No partially complete path coupled with populate properties seemed to work (and the model property doesn't seem to be necessary; makes sense since it is included in the schema). Took me a whole damn day to figure this out! Not sure why the other examples don't work.

(Using Mongoose 5.5.32)

User · Answer

It s is the best solution   Car   find     populate      path   pages page components

User · Answer

For someone who has the problem with populate and also wants to do this    chat with simple text  amp  quick replies  bubbles  4 database collections for chat  clients  users  rooms  messasges  same message DB  structure for 3 types of senders  bot  users  amp  clients refPath or dynamic reference populate with path and model options use findOneAndReplace replaceOne with  exists create a new document if the fetched document doesn t exist     CONTEXT  Goal   Save a new simple text message to the database  amp  populate it with the user or client data  2 different models   Save a new quickReplies message to the database and populate it with the user or client data  Save each message its sender type  clients  users  amp  bot  Populate only the messages who have the sender clients or users with its Mongoose Models   sender type client models is clients  for user is users      Message schema   const messageSchema   new Schema       room            type  Schema Types ObjectId          ref   rooms           required   true   Room s id              sender              id    type  Schema Types Mixed            type                type  String              enum    clients    users    bot                required   true   Only 3 options  clients  users or bot                         timetoken            type  String          required   true   It has to be a Nanosecond-precision UTC string              data            lang  String             Format samples on https   docs chatfuel com api json-api json-api         type                text  String              quickReplies                                          text  String                         Blocks  ids                      goToBlocks   String                                                   mongoose model  messages   messageSchema       SOLUTION  My server side API request  My code  Utility function  on chatUtils js file  to get the type of message that you want to save          We filter what type of message is         param  Object  message     returns  string  The type of message      const getMessageType   message   gt        const   type     message data      const text    text           quickReplies    quickReplies        if  type hasOwnProperty text   return text      else if  type hasOwnProperty quickReplies   return quickReplies             Get the Mongoose s Model of the message s sender  We use    the sender type to find the Model         param  Object  message - The message contains the sender type      const getSenderModel   message   gt        switch  message sender type            case  clients               return  clients           case  users               return  users           default              return null            module exports         getMessageType      getSenderModel       My server side  using Nodejs  to get the request of saving the message   app post   api rooms  roomId messages new   async  req  res    gt            const   roomId     req params          const   sender  timetoken  data     req body          const   uuid  state     sender          const   type     state          const   lang     data              For more info about message structure  look up Message Schema          let message                 room  new ObjectId roomId               sender                     id  type      bot    null   new ObjectId uuid                   type                            timetoken              data                    lang                  type                                                                                                         CONVERT THE MESSAGE                                                                  Convert the request to be able to save on the database          switch  getMessageType req body                 case  text                   message data type text   data type text                  break              case  quickReplies                      Save every quick reply from quickReplies                    message data type quickReplies     map                      data type quickReplies                      quickReply   gt                            const   text  goToBlocks     quickReply                           return                               text                              goToBlocks                                                                                     break              default                  break                                                                                        SAVE THE MESSAGE                                                                              We save the message on 2 ways             - we replace the message type  quickReplies   if it already exists on database  with the new one             - else  we save the new message                      try               const options                        If the quickRepy message is found  we replace the whole document                  overwrite  true                     If the quickRepy message isn t found  we create it                  upsert  true                     Update validators validate the update operation against the model s schema                  runValidators  true                     Return the document already updated                  new  true                             Message findOneAndUpdate                    room  roomId   data type quickReplies      exists  true                      message                  options                  async  err  newMessage    gt                        if  err                            throw Error err                                                 Populate the new message already saved on the database                      Message populate                          newMessage                                                        path   sender  id                               model  getSenderModel newMessage                                                      err  populatedMessage    gt                                if  err                                    throw Error err                                                              res send populatedMessage                                                                                               catch  err                logger error                    API Error on saving a new message on the database of roomId   roomId     err                      message  req body                                  Bad Request             res status 400  send false                       TIPs   For the database    Every message is a document itself  Instead of using refPath  we use the util getSenderModel that is used on populate    This is because of the bot  The sender type can be  users with his database  clients with his database and bot without a database  The refPath needs true Model reference  if not  Mongooose throw an error  sender  id can be type ObjectId for users and clients  or null for the bot    For API request logic    We replace the quickReply message  Message DB has to have only one quickReply  but as many simple text messages as you want   We use the findOneAndUpdate instead of replaceOne or findOneAndReplace  We execute the query operation  the findOneAndUpdate  and the populate operation with the callback of each one  This is important if you don t know if use async await  then    exec   or callback err  document   For more info look the Populate Doc  We replace the quick reply message with the overwrite option and without  set query operator  If we don t find the quick reply  we create a new one  You have to tell to Mongoose this with upsert option  We populate only one time  for the replaced message or the new saved message  We return to callbacks  whatever is the message we ve saved with findOneAndUpdate and for the populate    In populate  we create a custom dynamic Model reference with the getSenderModel  We can use the Mongoose dynamic reference because the sender type for bot hasn t any Mongoose Model  We use a Populating Across Database with model and path optins      I ve spend a lot of hours solving little problems here and there and I hope this will help someone

User · Answer

You can do this using  lookup aggregation as well and probably the best way as now populate is becoming extinct from the mongo  Project aggregate         match       id   mongoose Types ObjectId id             lookup          from   Pages collection name       let      pages     pages          pipeline               match       expr       in        id      pages                     lookup              from   Component collection name           let      components     components              pipeline                   match       expr       in        id      components                               as    components                        as    pages

User · Answer

I found this question through another question which was KeystoneJS specific but was marked as duplicate  If anyone here might be looking for a Keystone answer  this is how I did my deep populate query in Keystone    Mongoose two level population using KeystoneJs  duplicate   exports getStoreWithId   function  req  res        Store model          find            populate               path   productTags productCategories               populate                    path   tags                                      where  updateId   req params id           exec function  err  item                if  err  return res apiError  database error   err                  possibly more than one             res apiResponse                   store  item

User · Answer

That works for me    Project find query     lean      populate   path   pages        exec function err  docs         var options           path   pages components         model   Component              if  err  return res json 500       Project populate docs  options  function  err  projects          res json projects                   Documentation  Model populate

User · Answer

You can populate multiple nested documents like this       Project find query       populate          path   pages         populate            path   components          model   Component                    path   AnotherRef           model   AnotherRef           select   firstname lastname                      exec function err  docs

User · Answer

Remove docs reference  if  err        return res json 500     Project populate docs  options  function  err  projects        res json projects         This worked for me   if  err        return res json 500     Project populate options  function  err  projects        res json projects

User · Answer

I found this very helpful creating a feathersjs before hook to populate a 2 ref level deep relation   The mongoose models simply have   tables   new Schema          tableTypesB    type  Schema Types ObjectId  ref   tableTypesB            tableTypesB   new Schema          tableType    type  Schema Types ObjectId  ref   tableTypes              then in feathersjs before hook    module exports   function options           return function populateTables hook        hook params query  populate           path   tableTypesB         populate    path   tableType               return Promise resolve hook          So simple compared to some other methods I was trying to achieve this

User · Answer

If you would like to populate another level deeper  here s what you need to do  Airlines findById id         populate           path   flights           populate                           path   planeType               model   Plane                                     path   destination             model   Location             populate       deeper             path   state               model   State               populate       even deeper               path   region                 model   Region

User · Answer

As others have noted  Mongoose 4 supports this  It is very important to note that you can recurse deeper than one level too  if needed   though it is not noted in the docs    Project findOne  name  req query name        populate           path   threads           populate                path   messages                model   Message               populate                    path   user                   model   User

User · Answer

Mongoose 4 5 support this  Project find query     populate         path   pages        populate           path   components          model   Component                  exec function err  docs         And you can join more than one deep level

User · Answer

Mongoose 5 4 supports this   Project find query   populate     path   pages page components     model   Component

[node.js] Populate nested array in mongoose

Examples related to node.js

Examples related to mongodb

Examples related to mongoose