Node.js Deployd 404 error on dpd.get & 400 error on dpd.put when using id parameter

Question

Basically what the title says - I've been getting a 404 Not Found on all ids that I enter for "id":

dpd.items.get("id", function(results, error) {
 console.log(results);
});

And a 400 Bad Request on any value of "id":

dpd.items.put("id",{category:value},function(results, error){
 console.log("Record updated");
});

All the id values exist in the Deployd dashboard, and I am able to make get requests using any category parameters OTHER than ID.

Feels like I've tried everything at this point, please help!

score 0 · Answer 1 · answered Jan 26 '15 at 20:09

0

Deployd create crud API of any collection.
Make sure collection name is correct try to use
http://localhost:PORT/items/id .. if this will also give 404 then open
http://localhost:PORT/dashboard/items/events/
and On dashboard goto dashboard/items/events/ this will open ON GET panel, write there console.log(this.query)

and about 400 request , you write the code console.log(this.body) on http://localhost:PORT/dashboard/items/events/#put-panel

This is the way to debug your API, deployd have some issue but better framework to create API instantly

answered Jan 26 '15 at 20:09

Muhammad Ali

1,992
1
13
20

Yes, http://localhost:5000/items/"id" also gives a 404. Console logs this: Navigated to http://localhost:5000/dashboard/items/events dpd.js:61 GET http://localhost:5000/__resources/items/validate.js 404 (Not Found) dpd.js:61 GET http://localhost:5000/__resources/items/delete.js 404 (Not Found) – kartikshastri Jan 26 '15 at 20:43
This logs the query { id: '301' } which should work because there is a record with id 301 but I still get a 404. – kartikshastri Jan 26 '15 at 20:53
do you have data in collection? – Muhammad Ali Jan 26 '15 at 20:58
if http://localhost:PORT/dashboard/items/events/ have 404 means you are using wrong collection name – Muhammad Ali Jan 26 '15 at 21:00
Yes I have data in /items that shows in dashboard. dpd.items.get works when I use parameters other than "id", that's what's confusing. – kartikshastri Jan 26 '15 at 21:03
are you using correct id value... like d6a432c10ee6db5c – Muhammad Ali Jan 26 '15 at 21:05
Yes, the id value is correct and exists in the deployd dashboard – kartikshastri Jan 26 '15 at 21:13
this deployd bug use the query dpd.items.get({id:value},function similarly for put .....https://github.com/deployd/deployd/issues/191 – Muhammad Ali Jan 26 '15 at 21:22
Unfortunately that doesn't seem to address this issue :( – kartikshastri Jan 26 '15 at 23:24

docnoe · Accepted Answer · 2015-03-02T12:53:10.357

This error can occur if you insert documents through a different client than deployd.

From here:

MongoDB uses ObjectIds as the default value for the _id field if the _id field is not specified ... if a client does not add an _id field, mongod will add an _id field that holds an ObjectId.

Although the IDs created by mongoDB are visible in the deployd dashboard, they are not normal strings (like the IDs generated by deployd) and deployd does not find them when it's looking for a string.

Try to run a query like the following with any other mongoDB client (e.g. Robomongo):

db.yourcollection.find({_id: ObjectId("some_id_you_know_exists_in_collection")})

If it does not throw an error, the id is most likely an ObjectId that was not created by deployd.

Unfortunately, there is no easy fix. (At least not for big collections and complicated apps.) For SMALL collections I'd suggest to just duplicate the data into a new collection and let deployd create new IDs.

Quick, dirty and untested:

dpd.collection.get({}, function(res) {
    _.each(res, function(object){
        object.oldId = object.id //add id backup 
        delete object.id

        // post new object without id -> deployd creates a new id
        dpd.newcollection.post(object, function(res, err) {
            if(err) {
                console.log(err);
            };
            if(res) {
                console.log(res);
            };
        })
    });
})

You have to decide for yourself if that works for you.

This was in fact the problem, I was importing in data from a csv. Was able to solve the problem by importing w/o ids. — kartikshastri, Sep 02 '15 at 22:58

Node.js Deployd 404 error on dpd.get & 400 error on dpd.put when using id parameter

2 Answers2