https://netsuiteprofessionals.com logo
Join Slack
Powered by
Hey guys, picture that : Role created, under Setup...
# suitetalkapi
m
Hey guys, picture that : Role created, under Setup > Log in using Access Tokens, SOAP Web Services Employee created, role assigned Integration record created Access token created with above application, employee and role When sending request, I am getting 
Invalid login attempt
error This is in RP by the way. In Enable features I have : SOAP Web Services = T, Token-Based Authentication = T Any clues ?
c
What does it give as the reason in the login audit trail?
m
Recreated token and integration record since, let me send request again
execution log is empty
c
The Login Audit Trail in NetSuite is empty?
m
Correct, no results when checking for login audit for the Employee record used for integration
@CD ?
c
Are you saying that you can't see anything in the "Login Audit Trail" page? The actual page in NetSuite, not anything on the employee record. Sounds very unlikely if you tried to authenticate
m
correct it is empty
c
What are you using to send the request? Can you share the request? Are you hitting the correct endpoint? What URL are you using?
m
login audit trial detailed search with details column - for today shows only my logins and some sers I provided and access to RP
it is a custom platform my company is using, entirely home grown
b
that url has the wrong casing, but thats probably a problem for later
have you ever made a successful request to the soap webservices
m
in SB, but not in this version of RP
b
usual causes for a request not hitting the login audit trail is an incorrectly filled in field
that usually means the tokens are wrong
or the realm / account id is wrong
m
account id is xxxxxxxxx-rp as we test in RP The tokens are 100% correct, as generated them several times for this very project
c
you need to use an underscore _ instead of a dash - in the account ID in the SOAP header
Any news?
m
are you sure with underscore ?
c
inside the soap request header? yes
m
you mean in the POST query itself ?
should have dash not underscore
with _ I get the error Error: getaddrinfo ENOTFOUND 11111111_rp.suitetalk.api.netsuite.com
c
no
in the SOAP header
m
What is the KEY in the header you are refering to ?
b
SOAP Web Services Preferences is where you find the account id
m
yep, getting error
P.S. I know what is my account ID 🙂
b
Company URL is where you find the soap webservices domain
your past statements lead us to conclude that you dont know the account id, and that the account id is not in the company url
which is unusual, its a lesson you usually learn in sandbox
m
I know account ID, I was blanking it with xxxxxxxx and 111111111111 previously
b
account ids dont have hyphens in them
same thing for the url
m
well, my company url page says otherwise, has hyphen in it, had number of integrations in the past, always with hyphen
b
same thing, you dont know the account id, and you dont know that the accound id is not in the company url
m
I do know the company ID
b
take a look at the links i provided before to get the actual values you need to be using
m
SUITETALK (SOAP AND REST WEB SERVICES) url has hyphen in it
this is from company URL
c
We are not talking about the URL. I don't know how to be clearer that you need to specify the account ID with an underscore in the SOAP reuqest header
Like, the actual XML
There's no other way of saying this
It is what it is
b
hes making the mistake of assuming that the account id is in the company url
c
Copy code
<soap-env:Envelope xmlns:soap-env="<http://schemas.xmlsoap.org/soap/envelope/>">
  <soap-env:Header>
    <tokenPassport>
      <account>THIS_THING_HERE</account>
b
so when you said to use an underscore in the account id, he made the same change in the company url
m
<faultstring>No such operation 'checkasyncstatus'</faultstring> Getting this now, it is for SOAPaction
b
you are now at the point where you need to get the casing in your url's path correct
interestingly, a problem that would have also occurred in sandbox
m
so maybe you point where the casing is wrong ? as the https://1111111111-sb.suitetalk.api.netsuite.com/services/Netsuiteport_2022_1 was working fine
b
NetSuite WSDL and XSD Structure has an example of what the url should look like
m
I`m lost, give up
c
You're not lost. You just refuse to listen
If you actually read the messages and advice, you see straight away that it should be capitalised
Copy code
NetSuitePort
2 Views
Open in Slack
PreviousNext
Powered by