{"type":"error.SuiteScriptError","name":"SSS_SEARCH_ERROR_OCCURRED","message":"Search error occurred: Invalid or unsupported search","id":"","stack":["Error\n at Object.execute (/SuiteScripts/mtl_currency_suiteql.js2332)"],"cause":{"type":"internal error","code":"SSS_SEARCH_ERROR_OCCURRED","details":"Search error occurred: Invalid or unsupported search","userEvent":null,"stackTrace":["Error\n at Object.execute (/SuiteScripts/mtl_currency_suiteql.js2332)"],"notifyOff":false},"notifyOff":false,"userFacing":true}

AI generated answer (using internal Slack threads):

Based on the conversations, the

SSS_SEARCH_ERROR_OCCURRED

error with a

Search error occurred: Invalid or unsupported search

message is usually thrown when there is an issue with the search setup in SuiteScript. This could be due to a variety of reasons such as incorrect search type, invalid filters, or unsupported joins. In the first thread, the user was able to resolve the issue by loading a dataset configured the same way as the query in the script, instead of creating the query in the code. This resulted in a significant performance improvement and the error was no longer thrown. In the second thread, the error was caused by a filter issue in the search. Once the user corrected the filter, the error was resolved. In the third thread, the user was encountering an "unexpected error" when trying to run a summary search with formulas via script. The search worked fine in the UI, but not when loaded and run via script. The user suspected that the issue was with the columns definition, as replacing the columns with ones created by them resolved the issue. Another user suggested that the error might be due to trying to load a standalone search, which requires specifying the search type when loading the search. In general, when encountering such errors, it's recommended to check the search setup carefully, including the search type, filters, columns, and joins. If the error persists, try to isolate the issue by commenting out parts of the code and uncommenting them one by one to identify which part is causing the error. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******