My Stuff
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
No Limits. Just possibilities.
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
Comments
-
Case Resolved!! :) Our consultant (Rsult) found it. The field was designed to show on a purchase order to which sales order it is connected. It was limited to a list of only sales orders and therefore showed the error code. The workflow that's behind it, is now adjusted and I no longer get an error. Thank you for your…
-
Hi Pauline, Here some screenshots; Hope this clear things? If you need more info, please let me know. KInd regard, Ron
-
Thanks @Jeff Pineda-Oracle; I have changed my profile :) @Pauline Joy Cac-Oracle; I have found the field, but it only applys to Purchase and in the Validation & Defaulting tab it says; "Allow and Set Dependent Field Values to Null" I can continue after this error and this is still in Sandbox, but I wouldn't want this error…