-
Notifications
You must be signed in to change notification settings - Fork 36
Unable to Upsert #20
Comments
Same. @passitor did you ever figure this out? |
I discovered a bug that was causing upsert to fail for me: #23 |
That patch did solve my problem. Upsert now works. Here's a working cURL request to update the memo field on an existing purchase order:
|
It seems the details of the request have to be an element of array 'record_data' , this is not documented in the readme, and im not sure why its even necessary .... also that patch #23 is needed It should really return a fail or notice result if 'record_data' is not set or empty |
hayden-t |
I have uploaded my php helper, which has examples in it that work for me: #38 , bear in mind this is as i use it it with all my modifications as branched by me in the forks page. but have a look it may work still. |
Thanks, I am using Python for the request. I was able to get search.js, saved search.js, load.js, and initialize.js to work, but upsert.js fails. I'm sending it in a format such as: { As a test, I'm just trying to alter an existing inventory items record name. I have tried several different versions of the format but nothing works. If I remove ""single record action", Netsuite send back a notice saying missing parameter. I suspect something might still be off in my upsert.js. I altered the original like in #23 and "ephemer" change from the post "JSON examples for subrecords, sublists, etc. #14" _"_I got the debugger working and found the code in upstream.js should look like this: UpsertRequest.prototype.loadOrInitializeRecord = function() { Maybe I shouldn't have made both wildkatana and ephemer's changes? Thanks |
Using a Python oauth2 request: I finally got it working with this general format: { Thanks for the great project! |
I have deployed rest_suite but am unable to use the upsert request. I am trying to update the memo field on a purchase order. Based on the README I have built the following cURL request:
This fails to make any change to the purchase order record. However, the script appears to return a successful response:
If I change the internal ID and record type to nonexistent gibberish, I still get the same success message.
Is there something wrong with the format of the data I am posting, or is the upsert script somehow broken?
The text was updated successfully, but these errors were encountered: