Discussions
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Don’t miss your chance to meet our SuiteGurus—NetSuite Support professionals and subject matter experts with extensive experience in select product areas, including OneWorld, Advanced & Basic Accounting, Supply Chain Management, Receivables & Payables, CRM, Account Administration, and the SuiteCloud Platform. Full Conference attendees can prebook exclusive 30-minute one-on-one sessions for your product questions.
Spots are limited! Register through your Agenda Builder and find SuiteGuru under Agenda Enhancements.
Changing preferred form affects WSDL updates
I am using the NetSuite WSDL to update customers on a regular basis from an outside database. This has been working flawlessly for weeks. Today, our staff set a custom form to be the preferred form. This form does not have the fields that I am updating on it. At the same time, my update program began throwing errors, stating that I was unauthorized to update a certain field (custentity40).
We changed the preferred form back, but I think this is a serious flaw. The WSDL isn't using a form, so why is it bound to what is available on the form? I am also running the update program as a NetSuite admin, so I have full access to everything, yet, I get a message that I am unauthorized to perform the action.