I read Joe Son’s blog post about NetSuite Transaction Type Internal IDs. I thought to myself, “Self, that seems odd. Surely, the internal IDs are well documented in either NetSuite’s help text, or at the very least in the SuiteScript Records Browser”
No, they’re not, and don’t call me Shirley.
Plus, the internal ID of a Record Type is different than the internal ID of a Transaction Type, so don’t confuse the two. Record Types are database tables in NetSuite, while Transaction Types are an enumerated list of the various transactions that are available in the field “type”, which is found within the Transaction Search implementation of the Search API.
Then, I thought they must be documented in the SuiteTalk Schema Browser. They are, but the constants documented there are specific to web services, not SuiteScript. For example:
The Assembly Build transaction internal ID is “_assemblyBuild” in SuiteTalk web services, but is just “Build” in SuiteScript.
Most, if not all these issues should go away with the NetSuite Eclipse IDE plug-in, which should provide type-ahead and code completion capabilities. You won’t need to look any of these things up – they’ll all be presented to you when coding a transaction search, and all you’ll have to do is pick the right one. That all sounds great, and when I get the correct version of Eclipse installed, I’ll let you know if it actually works. Currently, my Eclipse setup is not allowing for type-ahead and code completion for some reason. Once I figure that issue out, I guess I’ll have another blog post to write.