I tried it right after it was released, so it does work. It's just rather different than the standard NS Operations.You would create an "Advanced Search" Operation against the NetSuite recordType that the saved search references, then add a filter to the operation referencing the "yourRecordType"|savedSearchId. You'd set the input parameter equal to the internalID of your saved search.Also be aware that custom fields aren't populated in the same way they are presented via the normal profiles. All the custom fields share the same element name, so you have to use instance identifiers and attributes to actually map from it.
Hi Adam,Thanks for the response. That's true. Also column tags were included in the NS request, which was causing the error. Column tags were included in the request due to fields that were selected in the options tab. Disabled all the fields and was able to query the records successfully. Appreciate your help.Thanks.
SavedSearch can be confusing. Biggest eye opener for me was not to include all fields in the XML profile. In my case, that was a solution for a "INVALID_SEARCH_FIELD_OBJ" error from Netsuite. This error was also in the logfile of Netsuite it self, not just Boomi. I'm not sure what the cause is but is has to do with custom fields in Netsuite. Anyway, I have a workaround.
Update: documentation for the Saved Search has been added to the reference guide: Performing a saved or advanced search in NetSuite
I'm starting to look at this and figure out how to pull a Saved Search from NetSuite that works into Boomi to push to a separate system (BI Tool). Everything I am reading says I have to re-create the search within Boomi's system - There is no way to call the Saved Search that is working in NetSuite, either by name or by Internal ID #?
That's not true - Ted's response above (with the screenshots) shows how to reference an existing saved search by id (the id is the id value starting with "customsearch")
Nevermind - I re-read things and think I've got it working.
Retrieving data ...