This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

Team, I am creating an invoice PDF based on an Advanced PDF template, but I have an issue when displaying the subsidiary logo when creating the PDF via suitescript (render.renderAsPdf). When opening it normally from the print button, it works fine. The template has the following to show the logo: &lt;td&gt;&lt;#if subsidiary.logo?has_content&gt;&lt;div top="-20"&gt;&lt;img src="${subsidiary.logo@url}" style="width: 230px; height: 40px;" /&gt;&lt;/div&gt;&lt;/#if&gt;&lt;/td&gt;. Anyone has experienced this issue?

you didnt actually explain what the issue was

sorry, the logo is not showing up when calling the template from suitescript vs printing the template from the NetSuite Invoice page

it's like the subsidiary object is not populated when calling from suitescript vs regular print

use <https://system.na0.netsuite.com/app/help/helpcenter.nl?fid=section_452452331542.html|render.transaction> if you want all the data to match

otherwise you need to fill in the subsidiary data source yourself

TemplateRenderer are too generic to guess the subsidiary for you

okay thanks, let me try the render.transaction

just to know, how could I fill in the subsidiary data source?

in this case, probably the same way you filled in the record

you mean, in addition to do this: rendererObj.addRecord({ templateName: "record", record: invoiceRecord });

the internalId of the logo used by standard pdf templates matches the internal id of the logo on a record, so you just use <https://system.na0.netsuite.com/app/help/helpcenter.nl?fid=section_456543212890.html|TemplateRenderer.addRecord>

if it didnt, you would use <https://system.na0.netsuite.com/app/help/helpcenter.nl?fid=section_4528541027.html|TemplateRenderer.addCustomDataSource>

okay, I thought you could only use .addRecord once

but you are suggesting we can use it more than one, adding the invoice record and also the subsididary record, correct?

as long as you dont use the same `templateName`

I will try both options you mentioned, render.transaction and also source both the invoice and subsidiary records, with different templateNames

great, the render.transaction works perfect, and it picks up the defined template too

gonna try the other approach now, just to know if it works

also works great by adding a second record

```// prepare render object with invoice record and subsidiary record
   const rendererObj = render.create();
const invoiceRecord = record.load({
   type: record.Type.INVOICE,
   id: nsInvoiceId,
   isDynamic: false,
});
   rendererObj.addRecord({ templateName: "record", record: invoiceRecord });
   const subsidiaryRecord = record.load({
       type: record.Type.SUBSIDIARY,
       id: invoiceRecord.getValue("subsidiary"),
       isDynamic: false,
   });
   rendererObj.addRecord({ templateName: "subsidiary", record: subsidiaryRecord });
   rendererObj.setTemplateByScriptId({ scriptId: InvoiceAPISettings.InvoiceAdvancedPDFTemplateScriptId });
   // render PDF file and save it to folder
   const invoicePDFile = rendererObj.renderAsPdf();```
