Discussions

Check out Oracle NetSuite upcoming events and conferences here

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.

Don't miss out on our Pop Quiz You only have until October 8, 2024, 2:00 PM ET to comment your answers and earn rewards! Click here for more details.

Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.

Get ready to take on exciting new challenges and become the next SuiteMaster of the Month!

AI capabilities embedded across the suite help boost productivity and give leaders an edge by helping them analyze data faster and generate unique insights that drive better decision-making. Watch these on-demand webinars to see how our AI capabilities can help you.

Streamline Invoice Processing with AI-Powered Automation

Use AI-Driven Insights for Faster, Better Planning and Forecasting

NSC | Referencing the Immediate Parent Customer from the Child of 2 levels or greater in Workflow

Jun 1, 2022 6:07AM edited Apr 25, 2023 8:40PM in SuiteCloud / Customization

When trying to get the value of the Parent Company field using {customer.parent} via Workflow for a child customer of 2-levels or greater, the top-level customer will be returned, not the immediate parent customer.

A workaround for this is to use the Client-side (i.e. After Field Edit, Before User Submit, etc.) formula below:

nlapiLookupField('customer', nvl(nullIfEmpty(nlapiGetFieldValue('entity')), -1), 'parentcustomer.internalid')

The above formula utilizes the 'parentcustomer' Search Join specified in the SuiteScript Record Browser instead of the 'parent' Field Reference.

Unfortunately, the above formula does not work for Server Triggers. So, if Server Triggers must be used, the only workaround is to copy the value of the