hello all,I AM new to soap webservices,i need to c...
# suitetalkapi
s
hello all,I AM new to soap webservices,i need to configure SOAP webservice to create estimate record,it throws a used error like "In this account, you must use account-specific domains with this SOAP web services endpoint" can u please guide me..Thanks in advance
b
the service port in the wsdl doesnt use an account specific domain
you need to change the domain you send posts to
s
thank you battk..do u have sample xml to create estimate record
<soapenv:Envelope <soapenv:Header> <passport xsi:type='platformCore:Passport'> <email xsi:type='xsd:string'>******</email> <password xsi:type='xsd:string'>*****</password> <account xsi:type='xsd:string'>*****</account> </passport> <applicationInfo xsi:type='platformMsgs:ApplicationInfo'> <applicationId xsi:type='xsd:string'>A60CBC90-B9EA-4064-B52F-E0D8C8784B3C</applicationId> </applicationInfo> </soapenv:Header> <soapenv:Body> <platformMsgs:update xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s0="urn:sales_2017_1.transactions.webservices.netsuite.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:platformMsgs="urn:messages_2017_1.platform.webservices.netsuite.com"> <platformMsgs:record xsi:type="s0:estimate" internalId="1"> <s0:itemList replaceAll="false"> <s0:item> <s0:item internalId="207" type="inventoryItem" /> <s0quantity&gt;1.0&lt;/s0quantity> <s0amount&gt;20.0&lt;/s0amount> </s0:item> </s0:itemList> </platformMsgs:record> </platformMsgs:update> </soapenv:Body> </soapenv:Envelope>
it returns error like page not found
b
your error is not in the request body
its in the url
s
this is the url that i have used
b
that looks like the correct domain in the url
make sure you get the right path
path should be the same as that in the wsdl
s
https://webservices.netsuite.com/wsdl/v2020_2_0/netsuite.wsdl sholud i use this as my wsdl? or i need to replace account id anywhere?
b
makes no real difference, all wsdls are identical
although you are using the wrong wsdl if your request body is using 2017.1