Hello, Depending upon when you were experiencing Paypal/ssp issues. There is a SuiteAnswer titled 'Integration with Third Party Checkout Providers' (Answer ID: 22788) that may be helpful. There is also a request to have this included by default in the Reference Cart bundle. As for getCustomFieldValues() not returning the…

There is a Customer method called 'getCustomFieldValues()', that could possibly be of use if the old checkout was sourcing from a custom field on the customer record. ie. nlapiGetWebContainer().getShoppingSession().getCustomer().getCustomFieldValues(); However, at this time it is only returning the internal ids of the…

Hi, thanks for checking. May I ask what version of IE you tried in? as it works for me in IE 8.

Hello, For 1, unfortunately, I was not able to determine how to have the fields saved during the shipping/delivery step. For 2, have both your fields enclosed in the same {....} portion [CODE] <a onclick='BDK.fire("customPlaceOrder",{"custbody1":$("custbody1").value, "custbody2":$("custbody2").value});return false;'…

I will have to look into the paypal payment type not working in the payment step. The bundle is not marked as Managed, so I believe it will not be pushed to any account that currently has it installed. I can't comment myself on whether or not any type of change log will be included with updates to the bundle. Thank you.

You can do this by making use of the validation.js library file in the js/libs folder. In your checkout_reviewinfo.txt file place your custom fields in a new form element, then modify the site.js to validate that form. &lt;form id="<span style="color:'"DarkOrange"'"><strong>customFieldsForm</strong></span>" action=""&gt;…

Hello, This may work for you, it is a bit lengthy in the post, but the actual changes are small: 1) In checkout_reviewinfo.txt (assuming it is at the review stage you have the custom field): Add your custbody field: [CODE]<label>Delivery Instructions?</label> <div class="f-input"><input type="text" id="custbody123" name=""…

Hello, Regarding 1) and 2). This is a possible defect. Please file a case with support regarding this. Regarding 3). Please try using .logIn instead of .login ('I' is capitalized). Please also file a case with support regarding this in order to have the help documentation updated. Thank you.

Hello, Try and copy the two library files NSCheckout.js and NSEmail.js from the /library folder to your custom ssp folders. Then, in your SSP Application (Setup > WebSite > SSP Applications). Under the Scripts > Libraries tab, try adding the two library files for: 1) Web Site Hosting Files/Live Hosting Files/SSP…

It seems you cannot use nlapiLookupField in your ss to grab the itemid field, as you will get a permission error. I do not see an alternate solution to this, you may want to file an enhancement request to expose the field in the commerce api. As for getting custom field values on the item record, you may want to vote for…

Hello, This is currently being tracked in Defect 221386 - Reference Cart & One Page Checkout BETA > Bundle 21011 > Password change/reset email link does not direct user to password change web store page. Please feel free to open a case with Support to be added to the Defect report. Thank you.

Hello, There is an existing enhancement for this request. Enhancement 182104 Sitemap Generator - Ability to automate Sitemap generation and uploading. Please feel free to vote for this enhancement via the NetSuite Support Center, or file a case with support. Thank you.

Hello, Installation instructions can be found in SuiteAnswers in the SuiteAnswer article 'Installing the Script Performance Monitor SuiteApp' Answer ID: 29871 Thank you.

Hello, I would suggest you remove the try/catch. Run the script again to trigger the Unexpected error noting the time it was triggered and then contact NetSuite Support to troubleshoot further. Thank you.

I saw you referencing tranid in your code, so thought you meant tranid. (even though you referenced internalid) If you are not set on coding this. Another option. - Create a saved transaction search - Criteria > Main line = T - Available filters tab - Internal ID - Type - Public = T - Save - Home tab - Personalize…

You can throw an error using nlapiCreateError in the before submit to prevent submission. However, if I recall, when the user clicks back to go back into the record, the data they entered will no longer be there.

Perhaps the users can just use the built in Quick Search portlet? -Home tab > personalize dashboard -Quick Search -Quick Search portlet > set up -Search type = Transaction

Hello, to clarify, are you referring to the new 2014.1 api nlapiVoidTransaction as opposed to nlapivoidrecord. There is no documented supported api called nlapivoidrecord. Thanks

The function name in your script is 'saveRecord'. You have likely mistakenly typed 'onSaveRecord' as the function name in the script deployment or custom form. Thank you

Hello, Enhancement 192354 SuiteScript > Expose savedsearch to SuiteScript exists to officially support this. Please feel free to vote for this enhancement. Thank you.

Hello, The SuiteAnswer article 'Job Manager APIs' (Answer Id: 26506) may be what you are looking for. It also contains a sample script for merging leads. Thank you.

Done. Thanks for letting us know!

Does removing the </xml> at the end of the xmlString help? xmlString += '</Table></Worksheet></Workbook></xml>';

Hi Steve, Thanks for the tip. I haven't reproduced this specifically with the @ or . symbols or order you specify. However, I have noticed that depending what you are sending the request with, if you have special characters in the password (nlauth_signature) value, you will get a 401 error. A way around this is to specify…

Ah, that explains it. Per the Help, the maximum password length in NetSuite is 16 characters. That password is 18 characters. If you removed the trailing 'd9' in the request it likely would have worked. Regarding the HTML URL encoding, I've posted this information in SuiteAnswer. SuiteAnswer ID 24977. Thank you.

Depending on the context/permissions, you could perform a nlapiSearchRecord() against the employee internalid and return the 'role' column.

nlapiGetRecordType() and nlapiLookupField(type, id, fields, text) may help you out. They are described in detail in the NetSuite Help.

Sounds like you are calling this from a client side save record function. In which case you will need to have your function return true; or return false; Naming the function afterSubmit does not mean it is an after submit script, it is just the function name. After submit scripts are deployed as user event scripts. You can…

That code is outside your if name == checks. Also, you should be setting the firefieldchanged value in your nlapiSetFieldValue api calls. You can read more regarding the firefieldchanged parameter in the api definition of nlapiSetFieldValue in the NetSuite help. Thanks.

I would think you would have to determine the API governance usage in your for loop and adjust your if statement value used with getRemainingUsage accordingly. SuiteCloud (Customization, Scripting, and Web Services) : SuiteScript : SuiteScript Reference : SuiteScript Governance : API Governance So for this script the API…