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

Is anyone having issues with PNG files in AdvancedPDFs? It just stopped working this week without any announcement or notice (that I can find in release notes)

We just sent out our billing and thousands of customers received an invoice with a big question mark.

Changing it to a jpeg fixes the issue but we need a PNG for the transparency properties designed in our logo.

PDF templates using transparent PNG logos are working properly in the two accounts I tried (on versions 2024.2.17.30132 and 2025.1.12.30183)

<@U08HZS41FE3> thanks for the reply. Support has confirmed that they have received multiple tickets regarding this but haven’t told us that it’s a defect or if use of pngs have been deprecated. 

Usually, whenever the image becomes a question mark icon, there is an issue in NS server

Make sure the url you use for your img src has its ampersand &amp; symbols escaped like so:
&amp;

or it may not parse the path correctly and the desired image will not show up in the PDF.

image.png

I've tried changing to jpg and still shows the question icon

Good luck. Our support case is still open 

I created a case. Hope NetSuite resolves soon.

We had to hire a designer to make us a temporary logo that works with our template background. 

If you use the 3rd link from the image record, the images should display correctly on the PDF.

Looks like we've had issues with the field imageurl since at least last week on pdfs. For us it's jpegs. Other custom fields are rendering as expected, but not imageurl.

For us the <http://ACCTNUM.shop.netsuite.com/core/media/media.nl?id=12345678&amp;c=ACCTNUM&amp;h=biglongnumbersandlettersstring>
URLs are not rendering in advanced PDFs anymore (I think they used to?)
But the other versions of the image file urls that use the app or secure subdomains (and https protocol) DO work.

I'm not sure if this is because of use switching from PDF Layouts to Advanced PDF Templates but I don't think it is or we'd have noticed on the record type that was already using advanced templates a long time ago.

In the meantime I'm fixing it by having the template use the app subdomain  and path, and tacking the url params on the end of that, for all the text field on all the transactions that use it.