Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Stay in the Know
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Upcoming Change for Numerical Field Value Comparisons
As of 2019.2, we have fixed an issue that occurs for workflows with conditions on actions containing client triggers that compare two numerical fields, such as decimal, integer, and currency fields. Currently, when a condition executes on client triggers to compare two numerical fields, the field values are treated as strings by the system. Instead of comparing fields’ numerical values, the system reads fields alphanumerically, character by character. As a result, the system may be returning incorrect results.
See the following table for an example of how the system used to treat strings:
| Condition in Workflow | Field Values | Expected Results | Actual Result |
Regards,
@Robert Nedelkow-Oracle | NetSuite Support Community Administrator
0