Ever built a Saved Search that crawls instead of loads? I have, and one small workaround I have found is to add &csv=Export to the end of the URL. This will trigger the CSV export automatically. So instead of needing to view the report and then click CSV export I can go directly to getting the CSV that I ultimately want. Full URL will end up looking something like this: https://[companyid].app.netsuite.com/app/common/search/searchresults.nl?searchid=1234 &csv=Export I have also used this for some external tools and Hot Key functions where I need the user to get the CSV file.
Sometimes it's the smallest slice of a project that demands the most ingenuity. What seemed like a simple enhancement to a Saved Search ended up stretching my understanding of NetSuite’s formula logic—and my patience. 🔍 The Objective I needed to compare two types of project actions occurring within a 30-day window. Here’s the twist: Project Actions are a custom child record of a NetSuite Project (Job) , and they’re not stored in a way that makes direct comparison easy. So, I had to retrieve them through a Project Search , pulling in individual Action records via joins—first hurdle cleared. 📅 Date Math, NetSuite Style Next came the math. I needed to calculate whether one action happened within 30 days of another, but NetSuite doesn’t make date arithmetic feel intuitive. My first instinct was to use TO_NUMBER() to convert the dates into values I could compute on. Spoiler: it didn’t work. So I tried a workaround—subtracting a fixed reference date ( TO_DATE('01/01/2000...