This article is relevant if you are seeking a signature on your outbound NetSuite email messages or you are developing code and and you are having trouble reading the ‘userpreferences’ configuration object.
For the longest time, I have struggled with the signature in my email messages that originated from NetSuite. Â Since I use a simple text based email signature, I was not thinking in terms of rich formatting. Â I simply cut-and-pasted my text based email signature into NetSuite’s user preferences and it worked — well, for the most part. Â I would struggle with the signature format at times when I would use the email messaging tool. Â It didn’t occur to me to think in HTML terms.
Recently, I wrote an article about how NetSuite will escape HTML for us — we can often forget about what is going on behind the scenes as we are producing SuiteScript based solutions. Â In this case, I was blinded by simply being too technical about what is going on. Â Yet, this text box gets a bit different treatment than others.
NetSuite’s TextArea Signature is Treated as Literal
NetSUite’s Signature is literal based. Â I would have learned this quickly by reviewing NetSuite’s field help which offers to use straight HTML. Â But this textarea is treated different than other NetSuite textarea elements. Â In this field, when you store HTML, you get back HTML. Â In the other articleÂ , the left and right braces are encoded. Â They are not encoded in this case. Â The good news is that the treatment here on this field makes using the signature easy to work with in Advanced PDF templates. Â Simply output it as is and you get HTML.
Help Fellow SuiteScript Developers
If you are a NetSuite SuiteScript developer and you have interesting things you have learned while working in the platform, please share you thinking. Â If you would like to work with our team, let’s have a conversation.