title: How to use subcriteria in populate (for example : .populate('something',{select:[]})) in sails js
body: <p><code>.populate('something',{select:[]})) in sails js .</code> for me its an ambiguous usage. Is there any alternate solution for the problem </p>
  
  <p>I used select inside populate ... but it shows sub-criteria doesn't work in this version of sails </p>
  
  <pre><code>Banktransaction.find(newData).populate('project_id',{select:['project_name']}).exec((err,banktrans)=&gt;{
                                      if(err){
                                          return res.json({
                                              error : err
                                              });
                                          }   
                                          if(!banktrans){
                                              return res.notFound();
                                          }else{
                                              return res.json({
                                                  'responseType':"success",
                                                  'responseMessage':"Banktransaction details founded successfully",
                                                  'result': banktrans
                                              });
                                          }
  
  
  
                                  });
  
  //result
  
  {
      "error": {
          "name": "UsageError",
          "code": "E_INVALID_POPULATES",
          "details": "Could not populate `project_id` because of ambiguous usage.  This is a singular (\"model\") association, which means it never refers to more than _one_ associated record.  So passing in subcriteria (i.e. as the second argument to `.populate()`) is not supported for this association, since it generally wouldn't make any sense.  But that's the trouble-- it looks like some sort of a subcriteria (or something) _was_ provided!\n(Note that subcriterias consisting ONLY of `omit` or `select` are a special case that _does_ make sense.  This usage will be supported in a future version of Waterline.)\n\nHere's what was passed in:\n{ select: [ 'project_name' ] }"
      }
  }
  </code></pre>