Troubleshooting

getting an error? getting a blank invoice? let's work through some common issues experienced script not running a common script error is when "sss invalid scriptlet id" is returned commonly this is because the script deployment has a status that makes the script inaccessble set status = released on the deployment to address this issue text or logos not showing in multi subsidiary orgs in multi subsidiary netsuite orgs sometimes company addresses or company logo's are stored differently than single subsidiary the templates either fail outright or may run and just not show a logo or address the reason for this is that the call to a subisidiary's logo or text elements might need to reference the record on which it resides inside of netsuite this is based on the record you clicked from, but coming from salesforce it does not exactly know to address the issue, you will need to edit the template's xml code either in netsuite, or by editing the downloaded template file and re uploading don't forget to update the internal id to match as necessary between breadwinner setup and the netsuite file if you're loading new files while testing through this first edit to try is prepending "record " before subsidiary in the merge code this means eg for subsidiary name, change ${subsidiary name} to ${record subsidiary name} as you find it in the xml if that doesn't work it may be necessary to create and use formula fields to do the heavy lifting netsuite's suitescript can then retrieve the correct logo file or desired text as referenced by the formula provided to create replacement formula fields for the template, you will create transaction body formula fields note ssn or tin used for taxid field, and subsidiary logo (forms) used for the logo url are sometimes not available if this is the case you must contact netsuite and open a case requesting access to those fields creating a transaction body field to reference text or logo fields this process is the same as creating custom fields for integrating from netsuite to salesforce, with some minor differences navigate to customization > lists, records, & fields > transaction body fields > new for text fields such as address or company name, it will be a free form text field un check "store value", and in apply to click sale in validation & defaulting tab, check "formula" and enter the old macro formula in the default value field note that below you can create a text field with source fields and can perform text formatting if you only wanted the name in this example however, you would just use {subsidiary name} save the field you will notice the id may be different from the name of the field if you did not specify it in the above screengrab you can see the id is custbody39 you will reference that id in the template file you are updating for use with breadwinner ${record custbodysubsidiarylogo\@url} for images (logos) the process is nearly the same create a new transaction body field just as you did for the text field above, however this time select image in the type field the applies to tab will be the same under sourcing & filtering tab, you will select the values as necessary notice the values selected below will retrieve the image from subsidiary (main) and are pulling the subsidiary's logo for forms you can adjust as necessary for your uses save the field you will notice the id may be different from the name of the field if you did not specify it in the screengrab for text field above, you can see the id is custbody39 you will reference the id in the template file you are updating for use with breadwinner in our examples next, that reference is now "custbodysubsidiarylogo" when the script processes your formula field, it likely can't handle the image as it does in the original template in this case you need to use the @url directive ${record custbodysubsidiarylogo\@url} finally wrapping the field in an img tag and adding the logo's actual pixel dimensions macro sections in xml for some reason it seems that netsuite developers like to cause confusion even though things "should" work they don't, or don't do so seemingly logicallly if it seems as though logo placement is correct and should be working, and are using a macro in the xml header, you might try a simple solution that is to put the url for the image somewhere in the standard \<body> section of the template, even though it's placement is not needed or wanted there / adding a p hide me style that does not render, we can add elements that are processed but never show up / ${record custbodysubsidiarylogourl\@url} this seems to cause the netsuite script engine to go ahead and process the logo, and once processed it will proceed to run correctly in the macro odd and unknown why this is the case, but it seems to work on occasion but wait, let's do something tricky as you really didn't want an additional line of url code on your template did you? / adding a p hide me style that does not render, we can add elements that are processed but never show up / ${record custbodysubsidiarylogourl\@url}