From NetSuite Support:

”

As per checking of your case message, I understand that your concern is about populating the ‘To Location’ and ‘From Location’ of your Inventory Transfer saved search and have them in one line only.

Per my initial investigation using the preliminary details you provided, I was able to confirm that functionality that you are looking for is an existing system limitation. Inventory Transfer saved searches are currently only allowing the ‘Location’ field to show both the ‘TO’ and ‘FROM’ locations in different line.

We understand that the aforementioned feature will be beneficial for you. Fortunately, there is already an Enhancement request logged for the same concern, details of the Enhancement are as follows:

178607 List > Search > Saved Searches > New > Transaction. Please include ‘To & From Location’ field that sources from Inventory Transfer.
I can attach this case to add a vote to the above enhancement. Our system engineers periodically reviews these enhancements and hopefully be implemented in our future releases. Please note that there is not specific time-frame for its release though.

”

Please upvote this Enhancement request (178607).
Thanks!

Ok, I think we are down to:

inventory transfer  -vs-  transfer order

Chris your solution is elegant and works for ‘transfer orders’, Thank you!

My company uses both ‘inventory transfer’ and ‘transfer order’ for slightly different purposes.

On ‘inventory transfer’ type, NetSuite is unable to connect/join the data in ‘to location’ and it always produces -none- result even though the form for ‘inventory transfer’ uses that field. I have a support case open and will update this thread on what NetSuite says.

Small change when sorting by Line Sequence Number, results are:

Store A, – line sequence number = 0
Store A, – line sequence number = 0
Store A, – line sequence number = 0
Store A, – line sequence number = 0
Store B, – line sequence number = 1
Store B, – line sequence number = 1
Store B, – line sequence number = 1
Store B, – line sequence number = 1
Store A, – line sequence number = 2
Store A, – line sequence number = 2
Store A, – line sequence number = 2
Store A – line sequence number = 2

Still end up with the From Location at the top and bottom of the list.

Indeed the single-quote copied from the forum was causing the error. Thanks!

Not getting the error now but am getting (which may help/confuse the other issue) the same location returned for ‘^[^,]+’ as ‘[^,]+$’.

Now it seems to not be an issue with those formulas (I think they are working as they are supposed to) but the data in NetSuite and thus what is shown in the results of NS_CONCAT({location}).

Those results look like this (Store A is the from and Store B is the to location) this is all returned in one field:

Store A,
Store B,
Store B,
Store B,
Store B,
Store A,
Store A,
Store A,
Store A,
Store A,
Store A,
Store A

This happens on all transfers even just one item transferred once from Store A to Store B.

‘^[^,]+’ is correctly pulling the first location in the list Store A

‘[^,]+$’ is correctly pulling the last location in the list Store A

The issue seems to be in figuring out why NS has the ‘from location’ listed 8 times and the ‘to location’ listed 4 times… and why in the jogged order it is in?

Again thank you for your assistance on this!

-Mike

Thank you Chris and battk for the fast answers!

Yes, if NetSuite would expose/use the Field ID: transferlocation in addition to Field ID: location this would be easy.

Getting closer but not preferable.  I am receiving:

With Internal ID as Group and NS_CONCAT({location}) as Max (or min, no difference)

• one line per internal ID <– good
• the column for NS_CONCAT({location}) as Max (or min, same results) has many ‘to locations’ (duplicates, looks like always 4 for the from location and 4 for the to location… happens to = the number of lines when the Internal ID is not set as Group… like as if the Max grouping function is not properly applying)  <– lots of not needed repetition making it hard to read
• the REGEXP_SUBSTR(NS_CONCAT({location}),’^[^,]+’) as formula text with Min or Max returns “ERROR: Invalid Expression“

Thanks,

Mike