NetSuite work order PDFs: fix fields, bins, and due dates (Advanced PDF/HTML)

What this post covers

• Fixing a field that is pulling from the wrong source (example: an “Overall Height” field)
• Reducing unnecessary page count by adjusting table layout (column widths, wrapping, padding)
• Adding Due Date visibility on the printed work order
• Showing bin location for both inventory items (native bin) and non-inventory items (custom field) in the same column
• Quick troubleshooting steps when a field “should work” but prints blank

Before you edit: make a safe copy of the template

1. Go to Customization → Forms → Advanced PDF/HTML Templates.
2. Open the template used by your Work Order print.
3. Click Customize (or Edit), then Save As to create a copy.
4. Test changes in a sandbox if you have one.

Step 1: Fix wrong field mapping (example: “Overall Height”)

• The template is referencing the wrong object (for example, record.item vs a line-level object).
• The field exists on a related record, but the template is referencing it as if it were on the transaction.
• The template is printing the text label, but you need the internal value (or vice versa).

How to find the right field name

• In the Advanced PDF/HTML editor, use the Field selector panel and insert the field again instead of retyping.
• Compare the inserted token with what is currently in the template.
• If the field is a select list and you need an ID, use .internalId in FreeMarker.1

Validate line-level vs header-level fields

• Header fields (top of the transaction)
• Line fields (inside the item list loop)

Step 2: Reduce page count by tightening the item table

• Overly wide columns forcing wrapping
• Too much padding/line-height in the item rows
• A field printing multi-line content (like a long description)

Common layout fixes

1. Shrink the columns that do not need space
• “Rush” should usually be a short column.
• Quantity columns can be narrow.
2. Prevent accidental multi-line wrapping
• For columns like SKU, Bin, or Rush, use a white-space: nowrap; style on the cell where possible.
3. Reduce padding and line-height
• Look for CSS that sets large padding or line-height on td or the row class.
4. Make headers compact
• If “Rush” is breaking into two lines, shorten the header label to Rush and reduce header padding.

Step 3: Add Due Date to the bottom of the Work Order

Where to place it

• Due Date
• Work Order number
• Optional: Location, Priority

Due date formatting

Step 4: Show bin location for inventory and non-inventory items (fallback logic)

• Inventory items often have a native bin value that prints fine.
• Non-inventory items may use a custom bin location field instead.

Conceptual logic

• If the native bin value exists, print it.
• Else if the custom bin location field exists, print that.
• Else print a placeholder (like —).

Example FreeMarker-style fallback (pseudocode)

<#-- inside your item line loop -->
<#assign nativeBin = item.bin?if_exists>
<#assign customBin = item.custcol_bin_location?if_exists>

<#if nativeBin?has_content>
	${nativeBin}
<#elseif customBin?has_content>
	${customBin}
<#else>
	—
</#if>

Step 5: Troubleshooting checklist when a field prints blank

• Confirm the field has data on the source record.
• Confirm you are referencing the correct level (header vs line).
• If it is a select field, confirm whether you need the display text or .internalId.1
• Look for conditional logic that might be hiding the output.
• Test with multiple work orders: inventory-heavy, non-inventory-heavy, long descriptions.

Optional next step: a “bin put away” worksheet view

• A saved search or report that lists PO lines with item + bin location
• A custom form or print that summarizes bin info for receiving

Need help cleaning up NetSuite templates without breaking them?