We are trying to create Invoices in NetSuite using a SOAP request. However, some of the Invoices don't get created because of warnings thrown in NetSuite. The response XML contains a "warning" node and a warning message. When doing manually through UI, we would just press "OK" to accept this warning and go ahead with Invoice creation. How do I bypass these warnings when doing through SOAP?
Check out the NetSuite docs here https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N3536574.html.
It says warnings will either be treated as errors, or ignored when performing requests via their SOAP api.
There is also a boolean setting you can include in the request preferences called warningAsError.
E.g.
<ns1:preferences xmlns:ns1="urn:messages_2022_1.platform.webservices.netsuite.com" soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0">
<ns1:warningAsError>false</ns1:warningAsError>
<ns1:ignoreReadOnlyFields>true</ns1:ignoreReadOnlyFields>
Related
web-service has token parameter. In swagger and postman I send get-request properly (status 200). In Poastman creating request is very easy because it has separate pages for parameters and headers.
As for Rest Debugger I couldn't create and sent right get-request( appears error 400).
I tried many ways but without success:
I write token in request parameter section of Rest Debugger as key-value pair like "token"= "abcd12345..."
or
I write base URL and resouce together in URL-field like:
https://testserver.com/currencies?token=abcd12345..... or
I write resource separately in resouce field of Rest Debugger and base -URL in URL-field
but in all cases server returns error 400:
"the token field is required".
screens of swagger, curl, postman and rest debugger.
We suppose that a better solution is to use Postman for this task, if it works as expected and is more user-friendly. But if it’s principal thing – you can do it in Rest Debugger.
Go to the “parameters” tab -> click the “Add” button -> change “Kind” field to “HEADER” -> “Name” field to ‘’token” -> “value” to your token value.
You can see that in Postman you use a header to send token value, but in Rest Debugger simple param – that’s why you get different results.
Try to define it as header.
Use Parameter section and use [HEADER] instead of [GET/POST]
I have designed an API REST service (with Bonita) to which I can perfectly connect with Postman, with the following parameters:
By the way, the x-www-form-urlencoded option that is selected comes from the Content-type application/x-www-form-urlencoded header that is not displayed in my screenshot. The official Bonita specification states that this header is needed and I always get a 200-OK status code as an answer.
How can I specify an equivalent request with the body part in a Mendix Call REST service in a microflow? Here is what I have so far:
I guess the body part should be specified in the Request tab, but I just don't know how to do it properly. I always get the following error message for my connector, which means that, whatever I specify, the username is not taken into account:
An error has occurred while handling the request. [User 'Anonymous_69a378ed-bb56-4183-ae71-c9ead783db1f' with session id '5fefb6ad-XXXX-XXXX-XXXX-XXXXXXXXb34f' and roles 'Administrator']
I finally found that the proxy setting was the actual problem. It was set at the project scope and simply clicking on No proxy in the General tab did the trick! (both services are hosted on my local machine so far)
I just had to fill in the dedicated Authentication field in the HTTP Headers tab then, with the correct credentials, to eventually log in my Bonita service.
I am trying to retrieve all test suits which contain a specific test case by test case ID.
I'm sending the following GET call:
GET https://dev.azure.com/{organization}/{DefaultCollection/}_apis/test/suites?testCaseId={testCaseId}&api-version=5.0
Instead of receiving the list of test suits I get the following response:
{"count":1,"value":{"Message":"The request is invalid."}}
If I add project to the request url, I get Page not found 404 error, so I assume, project name should not be there. But even without it I get request is invalid message.
Test Case ID is correct, I've tried several, and the response was the same.
What am I missing with this REST call? I didn't have similar issues with other calls.
I used the following Microsoft resource for reference:
https://learn.microsoft.com/en-us/rest/api/azure/devops/test/test%20%20suites/get%20suites%20by%20test%20case%20id?view=azure-devops-rest-5.0
Probably Azure DevOps Server 2019 not support in api-version-5.0 in this API call, so just need to remove it (then the call did with the default correct version):
http://azure-devops-server:8080/tfs/collection/_apis/test/suites?testCaseId=1
I am using install4j and I want to call rest api's from installer.
I have searched documentation for HTTP request action but not able to find, so my problem is,
I want to sent json with http request using post method, for that I have provided following properties:
Request Headers : Content-Type=application/json,
Form data = key1=value1;key2=value2;....keyN=valueN,
URL=http://localhost:8180/ng/app-setting
But I am not understanding, how to provide authentication details?.
When I run installer file http request execution is start and ask username password after that error message displayed which I was set in properties, But how installer provide exact error message? Because I am not getting what is exact error or what is response message/code?
Please provide the solution and documentation links.
Also let me know the steps how to provide http request (with REST) POST method with json.
how to provide authentication details
To set the authentication programmatically, set the system properties serverAuthUser and serverAuthPassword in the installer.
how to provide http request (with REST) POST method with json.
Currently this is not possible. I've added this to our issue tracker.
Update 2017-11-13
As of 6.1, when you set the "HTTP request method" property of the "HTTP request" action to "POST", a "Custom request body" child property is shown. If selected, the "Content type" and "Request body" properties can be configured.
I am using PostMan as a REST client to test this API method Cisco ACL Analysis API. specifically POST /acl/trace or getAClTracksStd (first go to Policy Analysis)
Here is my PostMan HTTP test call
Does anyone who is familiar with PostMan understand why I am getting this "Request method 'GET' is not supported" error from the server? I am making a POST HTTP request, not GET.(Selected from Drop down menu) It make more sense for me to get a input invalid parameter error or something.
Just to show that the endpoint url works, heres a HTTP test request that works
(same link, host->host API -> GET /host/{startIndex}/{recordsToReturn}
There's two issues that I'm seeing with your REST call. First, the error you're seeing is because the call needs to be preceded by "https://". Second, remove the interface IDs parameter and values. You should get a response with data after making these changes.
Your json looks erronuous (comma after the destIp) - and the server probably always responds with a default confusing error message in this case. (Postman is very well tested and it sends POST).