Running a saved search that takes, from the ui, like 30-60 seconds to load. However, in my map/reduce where I am doing search.load(""), it has been stuck in getting input data for 4 hours. Any idea of how this could be sped up, or if it's just a glitch?

Sounds like you got yourself into an infinite loop. 4 hours though it should've tanked itself by now.

man! the only thing in the getInputData is return search.load("mysearch"). So I don't think it could be an infinite loop on my side at least

This happens quite frequently in a particular client account of ours... They pay for Netsuite advanced support, and have yet to get a resolution on it. I will let you know if they ever give us any information.

Why is netsuite sooooo slow. 300k records shouldn't be that hard to pull data back on lol

Well it's more peculiar that you can run the search in the UI in relatively short order, but the script just takes hours and hours

Can you run the search in the console successfully by chance?

how would you run it in the console? Meaning like a client script and debugging into it?

Yeah in the console load the search and see if it runs. Kind of like what Sandii posted above but you actually do the search logic and run it

Seems like it did. I only returned 50 though

I'd run it a little more wide open. It sounds like its just a netsuite goof but if you can get the code to run in the console for all of it, it can pretty much confirm it

Is there a single line easy way to run it for all 300,000 in the console?

I’ve experienced this exact situation in several scripts with different saved searches. Netsuite hasn’t been much helping in figuring out the cause, but when I have more than about about 30-45 thousand results in a saved search, the time it takes for getInputData to complete starts to increase very badly. It doesn’t scale in a linear fashion above that. 90,000 results could take 4 times longer than 45,000. 180,000 results make take 6 times longer than 90,000, and so on. I have seen instances where gID ran for many hours when I had hundred of thousands of results, then finally the map phase started. There were no errors. My only solution so far is to limit GID to returning only the first 30 thousand results, then keep re-submitting the same M/R script task until there are no search results left.

that's ridiculous

yes it is

Also how many columns are you returning? a shitload of columns will slow it WAY down

yeah, try to reduce columns to a minimum, and avoid large text columns whenever possible.

My scenario of the search taking 12+ hours sometimes is only 3 columns, but they are Grouping/Summing by date so it's possibly related to that

We have seen this happen with searches only returning one or two columns, even just the internal id column. It definitely has something to do with the # of results.

@creece 2 columns

Sometimes, talking about my workarounds to Netsuite' out loud makes me feel like i’m describing an abusive relationship, and people hearing me are thinking/saying “that’s not normal” or “no one should have to put up with that”

require(['N/record', 'N/search', 'N/format'],
function(record, search, format) {

    const MY_SEARCH = search.load({
        type: search.Type.ENTITY_GROUP,
        id: 'customsearch789'
    });

    console.log(MY_SEARCH);

    const MY_SEARCH_RESULTS = MY_SEARCH.runPaged({
        pageSize: 1000
    });

    console.log(MY_SEARCH_RESULTS);

    var results = [];

    MY_SEARCH_RESULTS.pageRanges.forEach(function(pageRange) {
        MY_SEARCH_RESULTS.fetch({index: pageRange.index}).data.forEach(function(searchResult) {
            results.push(searchResult);
        });
    });

    console.log('# Search Results: ' + results.length);
});

Run this in the console and replace the searchId and type with yours. See if it'll give you the results

@creece it errored with this. grrrr { "error": { "code": "", "message": "null" } }

this might be a good time to try SuiteQL. I have heard it performs better, but haven’t had a good test case to prove it.

ohhhh, yeah I need to learn it

for a two column saved search, provided you don’t have a ton of filters, it should be an easy conversion

there are like 10 filters

yeah, that could be time-consuming. it depends on the filters

Think I may just convert it to a csv since it's 5mb (under the 10)

Here’s a basic M/R template for running SuiteQL. won’t help with converting a saved search to SuiteQL, but still handy. Interestingly, if just returning the query itself form getInputData, you don’t even need the N/query module. Otherwise, yes, the N/query module is needed to run SuiteQL ad-hoc throughout a script.

That's awesome @scottvonduhn! Is there a way to build or try the sql in netsuite?

@screnshaw https://timdietrich.me/netsuite-suitescripts/suiteql-query-tool/

Is there a helper for these queries? For instance, I want to get line level data on a sales order, which appears to not be in the transaction table without a join

transaction lines are indeed a join in suiteQL