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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
nlapiLookupField on SuiteFlow's set field value action
I would like to use a custom field value of joined list record on Workflow Action.
I tried the following formula, but it didn't work as we expected.
{custrecord_sw_voyage_year} + '_' +
nlapiLookupField('customrecord_sw_vessel_company', {custrecord_sw_vessel_company}, 'custrecord_sw_vessel_company_name') + '_' +
{custrecord_sw_vessel_name} + '_' + {custrecord_sw_voyage_number}
Cannot we use nlapiLookupField with variables as arguments？
Tagged:
0