[jokell]

I’m assuming that this is not possible, but just in case – does anyone know how to generate a saved search with multiple levels to drill down?

For example, I am searching a custom record that has sales data for each rep by customer, and there is one record per month. What I’d like to do is have a saved search that shows the data for the sales rep in total, then clicking down to the total by customer, then clicking down to the customer by month. Right now I can accomplish two levels in a single search, but I can’t do all three.

Any ideas?
This is a cached copy. Click here to see the original post.

[Olivier Gagnon NC]

You can create multiple saved searches, and then jurry-rig them together. You can use a formula to create a hyperlink with proper GET parameters that calls the next search, and so on.

[jokell]

Any examples of what a formula like that would look like?

[al3xicon]

I’ve attached some photos with captions to help walk you through this process – let me know if this helps.

[jokell]

Heh, and I thought I had finally figured out all the tricks for saved searches. Thanks for the pictures – they help a lot!

[al3xicon]

No problem

[jokell]

Okay going even further down the rabbit hole…

So I need to get the internalid of what I’m searching for, not just the name. But how do I get to something like this:

custom_record_field.linked_record.internalid

So, in other words, the internal id of a linked record? Here is a more thorough explanation: my custom record has a customer’s name on it, and we assign each customer a “financial location” (basically where we want their orders reported even if they buy out of territory). So the location isn’t on the record itself. Is it possible to do this without a crazy nested “CASE WHEN” statement to cover all of our locations?

[al3xicon]

Unfortunately, the short answer is no :-/

NetSuite Saved Searches do not allow for nested joins – you can basically only go one level deep. So it sounds like a messy CASE statement may be the only way to solve your particular problem, unless you want to store the internal ID on the custom record alongside the linked record.

[Author]

Posts