Skip to main content

Our current approach uses a formula that pulls department data from a NetSuite Actuals saved search. It looks up the department code and returns the department name if it is in the actuals report. However, for new departments that don’t yet have transactions, the lookup fails—defaulting to “No Department”—even though the department code and name already technically exist in NetSuite.

While we can hardcode logic (e.g., map department 239 to a specific name), this isn’t scalable. From what I understand, we can’t create a transaction list that syncs directly to the full NetSuite department list, since that’s not a saved search.

One workaround we’ve considered is exporting the department list manually from NetSuite into a Google Sheet and syncing that, but we’re hoping there’s a cleaner solution.

How do others or Pigment typically handle this situation when planning for future departments without actuals?

 

IF(ISDEFINED('NetSuite PL Actuals'.Department Pby lastnonblank: 'NetSuite PL Actuals'.'NS_Department ID']), 'NetSuite PL Actuals'.Department Pby lastnonblank: 'NetSuite PL Actuals'.'NS_Department ID'], "No Department")

 

 

 

 

Hey Lizhong,

Your best option would be to create a separate saved search that lists only the departments in Netsuite. This should not come from an actuals transaction list, but rather pull the departments directly from the department field (department table) in Netsuite. Then create a scheduled import in Pigment to load the saved search data into the Department dimension list. This way your Pigment department list will be synchronised with the Netsuite department list.

Reply


Ask your question here!

Terms & ConditionsCookie settings