[James Magness]

I’ve built a few reasonably complex bundles. With these I’ve abstracted a lot of config information and constants into a bundle_config.js script that is included as a Library Script.

When deploying i need to update the config file for a specific deployment. e.g. one suitelet includes a custom css file by netsuite url /core/media/media.nl?id=etc..

Is there a way I can have a file in a bundle but not have it update when the rest of the bundle updates i.e. keep the config file persistent.
This is a cached copy. Click here to see the original post.

[James Magness]

I may have a psudo solution.

after installign a bundle.

*Edit the config to be instance specific.

*Copy the config to a subfolder.

*After updating the bundle copy the subfolder config back ontop of the default bundle one.

I’ll feed back on how this goes.

[James Magness]

This appears to be temperamental. My new technique is to edit the config script from the Documents > SuiteBundles > Bundle XXXX. Use the browser and upload the correct config file.

This allows you to keep all the bundles in one directory (with different names) and still overwrite the same file on the server per instance?

Anyone got anything better?

[pjhaveri]

RE: Bundle Configs

I’m having the same issue. I have two version, basic and advanced, of the same feature. So there is a basic version bundle and an advanced version bundle. The code is the same for both versions, but they run differently depending on the version.

Currently, I have to hardcode the version as a variable at the top of one of the js files. I would rather have a config file to do that.

On another note, I tried using nlapiLoadFile to load a config file of my choosing, but I get the error: nlapiLoadFile is not defined.

[Author]

Posts