Skip to main content

How many times have you gotten a NetSuite email and thought: “Okay… but who sent this?” Scripts, workflows, saved searches - it can turn into a scavenger hunt.

There’s a faster way. Inspect the email headers.

In Gmail: open the message → ⋮ → Show original
In Outlook: open the message → File → Properties → Internet headers

Then search (Ctrl/Cmd + F) for:

  • X-MailingID — account / action info. If it’s a saved search, you’ll often see something like search=12345 (that’s the internal ID).
  • X-NetSuite — what kind of sender it was. Look after t= for values like:
    • Script
    • Workflow
    • SearchEmailTask

Once you know the type (and the search ID when it’s there), you can jump straight to the right place to edit it or shut it off.

Caveat: forwarded copies often strip useful headers. You need the original message (or a saved .eml), not a forward.

*Hat tip to Alan Isola for sharing the tip on LinkedIn.

Labels:

Comments

Post a Comment

Popular posts from this blog

Turning Saved Search Logic Into Insight: A Lesson in NetSuite Date Math

  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...
Post a Comment
Read more

PDF Issue in NetSuite after 2025.1 update

Came across a weird issue after updating to NetSuite 2025.1.  Our PDF Printing function was showing the underlying code for the PDF instead of rendering the PDF. Looked at many possible issues and discovered that it was in our header: old code had name : 'Content-Type:' , value : 'application/pdf' I removed the : and it worked as before name : 'Content-Type' , value : 'application/pdf' Found the solution on Reddit.  Posted to a StackOverflow:  pdf generation - How to Change NetSuite 2025.1 PDF Renderer Back to Previous Instead of BFO? - Stack Overflow
Post a Comment
Read more

NetSuite - Force Single Select on Multi-Select Field

Issue: We had a request from our Stakeholders to change a Multi-Select Field to a Single Select.  The Issue came up with this field being part of a bundle that we use.   We didn't want to deal with this being reverted or causing issues after we updated the bundle in the future, so I cam up with this work around. It is a Client Script that will throw an error to the user if they select more than one, and then it will reduce the selection to one option. /**  * @NApiVersion 2.x  * @NScriptType ClientScript  *  * 2025 Prevents multiple selections in a multi-select field * by showing an error message and removing the last selected value.  *  */ define ([ 'N/ui/message' , 'N/runtime' ], function ( message , runtime ) {     function fieldChanged ( context ) {         var scriptObj = runtime . getCurrentScript ();         var fieldName = scriptObj . getParameter ({       ...
Post a Comment
Read more