HTTPS-PUT request

Ask the community
,
1

I’m still a newcomer with Corvid.
I’m trying to write to a collection from an external app via HTTPS-PUT requests.
The collection has the following columns (all Text Fields and Form Submission permissions are set):
“Signal”,“Symbol”,“Company”,“Order Type”,“Timestamp”,“System”

Now I’m not sure if my JSON object is correct in this form (error is WD_VALIDATION_ERROR).

{
“signal”: “Buy”,
“timestamp”: “01.06.2020”,
“orderType”: “Market”,
“symbol”: “PFPT”,
“system”: “Disruptors”,
“company”: “Proofpoint”
}

Is there anything specific I need to take into account during the external transmission like ContentType oder Headers?
Thanks for your help!

2

What about your collection permissions? Are they correctly set?

3

Changed to Custom Use - Anyone can create,update for this collection and still not working with the same error.
Or do i need different permissions?

4

Made some further Tests with a Test Collection which has a single Text field holding a stock symbol.

Here’s the complete backend HTTP function:

export function put_updateTest(request) {
 let options = {
 "headers": {"Content-Type": "application/json"}
  };
 // get the request body
 return request.body.text()
    .then( (body) => {
 // update the item in a collection
 return wixData.update("Test", JSON.parse(body));
    } )
    .then( (results) => {
      options.body = {
 "inserted": results
      };
 return ok(options);
    } )
 // something went wrong
    .catch( (error) => {
      options.body = {
 "error": error
      };
 return serverError(options);
    } );
}

It seems to stuck on the Wix backend side. The error comes at least from this direction. The GET request works fine (if I change the permissions) but the PUT request has this WD_VALIDATION_ERROR Issue.

1266×489 108 KB

Any hints where the problem might be?

5

I don’t know. I’d try to open the CORS:

let options = {
        headers: {
 "content-type": "application/json",
 "Access-Control-Allow-Origin": "*",
 "Access-Control-Allow-Methods": "PUT,",
 "Access-Control-Max-Age": "*"
        }
    };
6

And why dont you use
request.body.json()
instead of .text and parse ?

7

Extended the CORS and replaced .text with .json.
No Change, same issue persist.

928×486 81.6 KB

8

Did you get this working in the end? I’ve got an (almost) identical issue, and despite multiple issues of this nature here on the forums, I haven’t seen any solution as of yet…