Hello All, I have a question regarding Basic PDF form template being rendered in a map/reduce script and sent as an email attachment. For the exact same basic pdf template and exact same packing slip custom form the rendered PDF is different when generated manually from an item fulfillment versus when it’s generated from the map/reduce script. The “manual” generated PDF includes a desired column field but the map/reduced PDF does not. Again, the same basic pdf template is being used in both cases. I have added a custom label on the basic pdf to “prove” that it’s the same basic template being used. Also, all custom Packing Slip forms have the desired field set to print. My question is: Could this be a Netsuite bug or is there something I am missing? I have tried both the following code in the map/reduce:

var transactionFilePDF = render.transaction({
  entityId: parseInt(transactionInternalId),
  printMode: render.PrintMode.PDF,
  inCustLocale: true
  });

var transactionFilePDF = render.packingSlip({
  entityId: transactionInternalId,
  printMode: render.PrintMode.PDF,
  formId: packingSlipFormId,
  fulfillmentId: transactionInternalId,
  inCustLocale: true
  });

Where does the desired column field come from?

Hey Eric! The desired field is the out of the box lot number’s expiration date as per screen captures below.

Interesting; the only suspicion I had was that maybe it was a field/value added by a script or workflow that wasn't running in the M/R context.

My feeling is that this is a Netsuite issue. I have a Netsuite case going with them but so far I am not hearing anything concrete back from them. A colleague suggested I try to see if anyone else had come across this or if there was something I was missing. I’ll let you know what they end up saying. Thanks for your help.

Any time 🙂

@erictgrubaugh so the issue is with 2.1 apparently. According to Netsuite works fine with 2.0 or 2.x.

Oh fun

🙂