Anyone experiencing issue with Transaction PDF ren...
# advancedpdf
m
Anyone experiencing issue with Transaction PDF rendering the images and showing famous NetSuite ? mark icon?
s
Yes, our logo image stored in the file cabinet appeared to be broken this afternoon (Sydney time) so I've temporarily switched to an image on our web host which appears to be fine and will come back to it tomorrow
s
same here, not only images but also vietnamese font
a
yeeeep
e
Check the URLs of your references. If they have na.system or na2.system they have been depreciated. They should all start with your account number 12345.app.netsuite
From 2020.2 Release notes: Account-Specific Domains Supported in File Cabinet NetSuite 2020.2 supports account-specific domains in the File Cabinet. You should use account-specific domains in the File Cabinet instead of data center-specific URLs. Previously, NetSuite domains were specific to the data center where your account was hosted. Links in the File Cabinet used these data center-specific domains. NetSuite domains are no longer specific to data centers. Instead, they are account-specific domains, which are domains specific to your account and not to the data center where the accounts are hosted. For more information, see the help topic URLs for Account-Specific Domains. Some files in the File Cabinet contain links that use data center-specific URLs. You should change the URLs in those files to be account specific. For example, you should change a system.eu2.netsuite.com File Cabinet link to .app.netsuite.com, where is a variable representing your account ID. You can use the Traffic Health feature to identify links that should be updated. For more information, see the help topic Traffic Health Reports. If you attempt to create an email template using the data center-specific URL format, you will receive a warning message instructing you to use an account-specific domain URL instead. For more information, see the help topic How to Transition from Data Center-Specific Domains
s
Thanks for the info @ericbirdsall. Our URLs for the logo had already been updated, so this doesn't appear to have been the problem for us. We also had issues with a scheduled script unable to reach a suitelet (also using account specific URL) so it appears to have been a wider issue with file cabinet references (there's a small thread on the #C29GDT351 channel about it too).