I need to validate which fields I receive ${transaction_type} for this SOAP. I tried for example Sales Order, but I get the error: ?xml version=“1.0” encoding=“UTF-8”?<soapenv:Envelope xmlns:soapenv=“http://schemas.xmlsoap.org/soap/envelope/” xmlns:xsd=“http://www.w3.org/2001/XMLSchema” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>soapenv:Bodysoapenv:Faultfaultcodesoapenv:Server. userException/faultcodefaultstringorg.xml.sax.SAXException: Sales Order is not a legal value for {urn:types.core_2023_2.platform.webservices.netsuite.com}RecordType/faultstringdetail<ns1:hostname xmlns:ns1=“http://xml.apache.org/axis/”>partners211/ns1:hostname/detail/soapenv:Fault/soapenv:Body/soapenv:Envelope' ?xml version="1.0" encoding="UTF-8"? <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:platformCore="urn:core_2023_2.platform.webservices.netsuite.com" xmlns:filecabinet="urn:filecabinet_2023_2.documents.webservices.netsuite.com" xmlns:sales="urn:sales_2023_2.transactions.webservices.netsuite.com"> soapenv:Header tokenPassport account${acount}/account consumerKey${consumerKey}/consumerKey token${tokenId}/token nonce${nonce}/nonce timestamp${timestamp}/timestamp signature algorithm="HMAC-SHA256"${signature}/signature /tokenPassport /soapenv:Header soapenv:Body attach xsi:type='platformMsgs:AttachRequest' attachReference xsi:type='platformCore:AttachBasicReference' attachTo xsi:type='platformCore:RecordRef' internalId='${transaction_id}' type='${transaction_type}'/attachTo attachedRecord xsi:type='platformCore:RecordRef' externalId='${file_internalId}' type='file'/attachedRecord /attachReference /attach /soapenv:Body /soapenv:Envelope

AI generated answer (using internal Slack threads):

Based on the conversations, it seems like the users are encountering issues with SOAP requests in NetSuite. Here are some insights from the threads: 1. In the first thread, the user is getting an error when trying to set the order type field in a SOAP request. The community suggests that the order type field is not a custom field and should not be set manually. It is recommended to get an existing sales order to see how the field should be set. If the order type is mandatory and the user doesn't know how to set it, it is suggested to make the order type not mandatory for the form they are working with. 2. In the second thread, the user is getting an error when moving from WSDL version 2013_1 to 2013_2. The community suggests that the error is due to an invalid '?' value in an attribute or element. It is recommended to replace the '?' with a real value. 3. In the third thread, the user is trying to upload a file to a transaction using SOAP APIs but is getting an error. The community points out that the 'owner' field in the request is a recordref, and the internal id should be an attribute, not an element. Remember, these insights are based on the specific issues and solutions discussed in the threads. The actual solution may vary depending on the specific details of your SOAP request and the NetSuite configuration. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******