soap issue setting altname on a custom record in n...
# ask-stanley-ai
c
soap issue setting altname on a custom record in netsuite "NETSUITE_SOAP_FAULT: com.netledger.schemabean.NLSchemaBeanException: altname not found on {urn:customization_2021_1.setup.webservices.netsuite.com}CustomRecord [Not accessible. Value obtained from method: getDetailedDescription()]"
c
AI generated answer (using internal Slack threads):
Based on the conversations provided, the issue seems to be related to the
altname
field not being found on the custom record. This error is likely due to the fact that
altname
is related to auto-generated numbers. If no entity uses auto-generated numbers, then
altname
does not exist. In the first thread, the user was trying to create a custom record using SOAP webservices and encountered an error. The solution provided was to use the internal id of the record type, which is a number, not the script id. In the second thread, the user was having a problem with a Saved Search from an entity record type. The error was that the
altname
field does not exist. The solution provided was that
altname
is related to auto-generated numbers and if no entity uses auto-generated numbers, then
altname
does not exist. In the third thread, the user was having an issue with the SOAP address in the WSDL. The solution provided was to set up the SOAP client with the proper URL, as no WSDL will give the correct port. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.838739872
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.82516855
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.821390867
Please provide your feedback on this answer.