Hello Everyone,
Here facing an issue with Usereve...
# suitescriptp
Praveena Reddy
07/18/2023, 6:24 AMHello Everyone,
Here facing an issue with Usereventscript which is deployed on the Project master and the system is trying to call 3rd party URL in Usereventscript when the project master is updated in the rest API. Is any one faced same issue , could you please help us with resoloution.
Below is an error message.
{
errors: [
{
message: "Error connecting to database"
}
]
}
c
CD
07/18/2023, 6:33 AMAre you saying that error is coming from the 3rd party URL?
p
Praveena Reddy
07/18/2023, 7:19 AMIt's coming from NetSuite. the URL is working fine on the UES script when the project master is updated through SCH script or UI modification on the Project master. It's not working when restapi is calling the UES script.
b
battk
07/18/2023, 7:26 AMwhich line of code is throwing the error
p
Praveena Reddy
07/18/2023, 7:40 AM Copy code
https.putb
battk
07/18/2023, 7:40 AMthat implies the error is not actually from netsuite
battk
07/18/2023, 7:41 AMits from your third party
c
CD
07/18/2023, 7:42 AMMight be a good idea to familiarise yourself with tools like Postman
b
battk
07/18/2023, 7:42 AMyou also want to be very precise about how/what is happening with the error
battk
07/18/2023, 7:43 AMan error that is thrown from https.put is very different than an error written in the body of the response of https.put
p
Praveena Reddy
07/18/2023, 7:43 AMthe concern here is the URL https.put is working when we manually update the project and UES is able to call 3 rd part url. but it's not working on rest api when we tried to call on the project update
b
battk
07/18/2023, 7:44 AMthats more comparing the parameters from a successful request to your failed request
c
CD
07/18/2023, 7:45 AMShare your code then. Impossible to help you at the moment
p
Praveena Reddy
07/18/2023, 7:46 AMfunction get_JWT_token() {
//************************Token Generation steps*****************************//
var commonHeader = {
"Content-Type": "application/json",
"accept": "application/json"
};
var tokenURL = 'https://XXXXXX/get_NS_tokens';
var tokenMethod = 'POST';
var tokenBody = {
"userName": "XXXX@XXXX",
"password": "yyyyyy"
};
var tokenBody = JSON.stringify(tokenBody);
var tokenResponse = https.request({
method: https.Method.POST,
url: tokenURL,
body: tokenBody,
headers: commonHeader
});
var tken = JSON.parse(tokenResponse.body);
return tken;
}
b
battk
07/18/2023, 7:47 AMalthough that is not what you shared in the beginning
battk
07/18/2023, 7:47 AMthe debugging process is the same
battk
07/18/2023, 7:48 AMlog
Copy code
{
method: <http://https.Method.POST|https.Method.POST>,
url: tokenURL,
body: tokenBody,
headers: commonHeader
}battk
07/18/2023, 7:49 AMin the case where they are the same, then just hardcode the request parameters to be whatever generates a successful request and then trigger it via the rest api
battk
07/18/2023, 7:49 AMto double check
battk
07/18/2023, 7:49 AMgeneral idea is to figure out whats different, if you cant, then at least start from something that should succeed
p
Praveena Reddy
07/18/2023, 8:07 AMvar tken = tokens from previously shared code;
var request_header = {
"Authorization": "Bearer " + tken.jwtToken,
"Content-Type": "application/json"
};
var json_body = updated_json;
var encryptData = encryptionData(json_body, crypto, encode, 'XXXX');
var response = https.put({
url: 'XXXXX', // update base Url NIS-7513
body: JSON.stringify(encryptData),
headers: request_header
}); facing issue while calling PUT method of 3rd partly url
b
battk
07/18/2023, 8:11 AMthats going to be more annoying to compare if your body is encoded
battk
07/18/2023, 8:13 AMsame idea though, compare the input to the encoding function of a successful request to a failed request
battk
07/18/2023, 8:13 AMand in your case, for testing purposes, you should probably use the same jwt token if it last long enough