[JohnCCole]

I hadn’t done any major testing on my sandbox since the transition to system.netsuite.com until today and it appears relative paths to script files are broken.

Little more background I have some custom Suitelets who’s layouts are controlled by a template file. In the template I have html markup and references to javascript files in the file cabinet. The urls of the javascript file are relative /core/media….

Perhaps this method of having a view represented in a template file with javascript src references to files in the file cabinet is un-conventional but I don’t understand why NetSuite had to change the c and h parameter of file references on the sandbox after this NA sandbox transition.

A relative file path that used to look something like this regardless of what domain you were on (system.netsuite.com, system.sandbox.netusite.com and system.na3.netsuite.com in my experience)

/core/media/media.nl?id=123456&c=someaccount&h=123somevalue&_x t=.js

after the sandbox refresh becomes something like

/core/media/media.nl?id=123456&c=someaccount_SB1&h=123somevalu e654&_xt=.js

So I guess I’m either making all these files available without login or having to tweak my template code to generate all the script src paths on the fly using nlapiResolveURL or pulling the url from the file record itself or a search result.

In my testing for this I also noticed something that made me pause and wonder if it was working as intended. Are the custom scripts we create going on a CDN? I have a javascript file that is not available without login but yet I can take the URL for that file to a browser that is not logged in to NetSuite paste it in and the file will download.
This is a cached copy. Click here to see the original post.

[Author]

Posts