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!
Update your Profile with your Support type to get your Support Type badge.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
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
Nest Decode into NVL2?
We use a secondary address for Vendors on our PO in specific scenarios. Because of this we have setup some saved searches with an NVL2 formula to pull the secondary address if its being used in place of the billing address.
For the state results we use this formula:NVL2({custbody_vr_removal_add_addressee},{custbody_vr_removal_add_state},{billstate})
The issue we are having is that when the results are returned, the {custbody_vr_removal_add_state} variable will return the full name, New York, and {billstate} will return NY. This makes it difficult to parse the data by state alone.
Tagged:
0