Strange bug with REST API

RE: Strange bug with REST API

Josh Wright — Wed, 27 Mar 2019 18:33:32 GMT

Oh no, I figured it out as I replied above. Apparently if you don't use

read, create, update, delete

In Place of

GET, POST, PUT, DELETE.

Then app.api.call will actually only send GET requests instead of POST requests (Despite using 'POST' as the first argument). I assumed (wrongly) that Sugar would stick to the same CRUD commands that have been standardized and used for a long time, instead of abstracting them away (for what purpose I have no idea).

RE: Strange bug with REST API

Francesca Shiekh — Wed, 27 Mar 2019 17:24:00 GMT

If you are calling the api from within the application, the user is authenticated and already has a token, you will not need to request another or refresh it. The app takes care of that.

I believe you should use POST to create a new record, PUT to update an existing one. Clearly if you are updating it will need the id of the record to update. But if you are creating a new one, you won't have an id until after it is created.

Perhaps it would help if you could share your custom API. I totally understand if you can't.

Francesca

RE: Strange bug with REST API

Josh Wright — Wed, 27 Mar 2019 17:00:01 GMT

I actually found the issue. Apparently the app.api.Call method actually remaps 'POST' as 'update'. My fault, but I don't really understand why this would be done instead of just using the proper http methods. Why add another layer of confusion? I find myself asking this question a lot when dealing with Sugar. Thank you for trying.

RE: Strange bug with REST API

Josh Wright — Wed, 27 Mar 2019 14:55:40 GMT

I tried both

var app_url = app.api.buildURL('/<endpoint name>/<endpoint method>?=' + <put querystring here>);

as well as

var app_url = app.api.buildURL(<endpoint name>, <endpoint method>);

I read in the documentation The attributes hash must contain id of the resource being actioned upon for record CRUD and relatedId if the URL is build for relationship CRUD. I don't really have those as it is a custom endpoint.

and wasn't sure whether I needed those for my use case. I was using query strings for now during testing.

Quick question from the original post though, somewhat related. If I do end up getting this to work through Sugar's method of api calling, will it bypass the authentication requirement of getting tokens and refreshing them? (Instead, using the user's own base token). I honestly feel a lot more comfortable using JavaScript's Fetch API, it's a lot better documented and usable anywhere and not just within an obscure platform.

RE: Strange bug with REST API

Francesca Shiekh — Wed, 27 Mar 2019 14:43:20 GMT

When calling the api from your javascript are you building the url as described here?

Documentation Class: Api

e.g.

var url = app.api.buildURL("Contacts", "duplicateCheck", null, {});

e.g. I have custom a GET api that returns currency based on country:

var url = app.api.buildURL('/ERPCurrencyLookup/' + address_country);

FrancescaS