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
-
Did this ever get resolved? Having the same issue myself.
-
I understand what the error says. But I do not receive that error when I run this trigger in SB. Why would I receive an error in Production when the process works in SB? Something should not work in one place but not the other. Is there an enabled feature that effects workflow triggers? They are exactly the same in both…
-
It is a custom record that is living on the native NetSuite project record. I do not want to share full workflow for confidentiality, but functionally it is two states. State 1 is setting workflow field values that are stored based on what is in the record. State 2 is restoring those values and comparing them, and then…