@User_LJQX7-- Thanks again, Tigran. I had actually come across this myself just the other week and forgot to follow up on it in the thread here to list the solution and mark it as resolved. So now I'll mark yours as the answer instead. 👍️

@User_LJQX7 Perfect! Yes, it is a field added to a Sales Order record as part of a bundle. I had assumed it was a native field and hadn't bothered to look into the custom Transaction Body Fields. I found my answer right away once going there. Cheers!

@Dominica Sevilla-Oracle Do you know whether there is a way to have that check box marked by default? So that users don't have to remember to check it every time?

@Joahnna Given Uy-Oracle-- Certainly. Here is a screenshot of the Billed Sales Order: And here is a screenshot of the Pending Approval Sales Order:

@Joahnna Given Uy-Oracle-- No, the status of the Sales Order does not seem to play a factor in whether the Work Order # prints on the form. Regardless of status, we always get Yes or No when we try to utilize the {item.createwo} field. Here is the printout from a Sales Order that has a status of Pending Fulfillment: And…

Hello, @Joahnna Given Uy-Oracle-- Thank you for the input; however, as I mentioned to Miguel above, when we utilize the {item.createwo} field, we get a "Yes" or a "No" value in the PDF: Is this unique to our environment? We are using the Netsuite CPQ Configurator bundle (108493), so do you think that might be changing our…

Good day, @Joahnna Given Uy-Oracle-- For example, if we take the Sales Order shown below, we want to list both Work Order numbers (WO-103 and WO-105) on our customized Sales Order PDF printout: However, we do not know a way using Freemarker to be able to print the Work Order number onto the PDF. We are able to print the ID…

Hi, @Miguel Ariza - Sol4IT -- Thanks for the tip. We had already tried that one, however--all it does is print "Yes" or "No" depending on whether a Work Order has been created for that item line. So it's still not quite the information we're looking for.

Our users are at the point where they don't even WANT to use NetSuite until this defect is fixed--we just went live a few weeks ago and to have this happen so suddenly is certainly not helping with their acceptance of the new system.

In that case, then, @Michelle Jabanes-Oracle, is there a way to NOT send those Delivery Status Notification emails? Is there a way that we can turn them off?

Good day, @Michelle Jabanes-Oracle-- This might have been our mistake. This was happening on Item Fulfillment records, but it seems to be that the customer name is not clickable for any role (even Administrators) on those records-- meaning that this is likely standard NetSuite behavior for that transaction type. After…

I am facing a similar issue as you, @Benjamin Paul - USA. We are trying to read the value of {record.createdfrom.actualshipdate} in an Invoice PDF template by tracing backward to its associated Sales Order, but in our case what is being printed is the Estimated Ship Date of the Sales Order, not the Actual Ship Date. And to…

Yes, I have. When I do, I get this message upon template validation: So should I be using something other than record in the freemarker?

That did the trick, @Michelle Jabanes-Oracle. After giving a specialized role Full permission level to the Sales Order record those users were able to remove the messages. Much appreciated!

@Jack Daryl Espiel-Oracle: Thank you for that information. It worked perfectly! Very useful to know that we can use {shipzip} directly like that. Can we do the same with shipping/billing address fields like so: {shipaddress1} {shipattention} {shipstate} etc.?

@paul.baudouin, may I ask how you created that custom hyperlink? We are using File Drag and Drop and are attempting to put a custom transaction line field on each line that would be the URL to the attached file for that line (we know that we can see the file by clicking on the item row and then selecting "Show Files from…

Excellent. Fantastic. Exactly what we needed. Much appreciated, @Jack Daryl Espiel-Oracle.

@Joahnna Given Uy-Oracle -- We were ultimately able to get the signature to work by using this package here on pub.dev and modifying some of the code: https://pub.dev/packages/oauth1 The issue seemed to be due to how we had been encoding the data prior to generating the signature key and base URL (UTF16 instead of UTF8)…