Netsuite in the UK have said we can only have the 3 dev accounts if we sign up for a new sandbox account. They're apparently not available with our existing one for some reason :rolleyes:

According to a table dump sample we've got here, category image fields are likely to be: StoreDisplayImage_InternalId StoreDisplayImage_Name StoreDisplayThumbnail_InternalId StoreDisplayThumbnail_Name I know not all of these are accessible in searches though, even using the obscure Lists > Website > Category > Search >…

I hit the same issue trying to pull all of our sitebuilder data out into an external SQL database so we could build an external site which interacted with Netsuite's shopping cart. In the end, I had to write a restlet which uses the undocumented (possibly unsupported) nlapiSearchRecord('sitecategory',null,null,columns),…

Still doing it for me too - EU2 datacenter, 2018.2. It's actually now far worse, as once you experience the error, you get "Your session has timed out. Please log in again."

Painfully slow on EU2 at the moment for us.

We were fine all day yesterday as far as I'm aware too (UK / EU2).

khultquist No, we're using all Netsuite functionality.

We've had a load of these as well.

We have domain keys set. It's obvious that there was some sort of network issue with Netsuite which lead to this issue.

TTFB is slow for our sites, as is often the case during peak periods, but otherwise OK. We're UK/EU as well.

Sound a lot like it could be a saved transaction search with "Send Email Alerts When Records are Created/Updated" enabled within the email tab? Where that's the case, the first web services operation is the create event which would trigger the email.

Worryingly https://checkout.eu2.netsuite.com/ also seems to be affected. My interpretation is that this has effect from March 15th 2018. Was that how you read it too?

We're EU hosted and have similar issues with CSV imports at the moment.

If it's working for smaller groups, I'd check Setup > Company > View billing information and see if you're exceeding your account's provisioned limits.

I logged a case with Netsuite about it yesterday. It might be worth doing the same so they're aware that it's more than just one account affected.

https://browser-update.org/ provide an easy to install javascript out-of-date browser notification script. It uses browser detection, so won't disturb unaffected users and the text can be customised, so you could word the message to suit your own preference.

SiteBuilder places a hidden "server commands" iframe in the bottom of pages with the target URL empty.html. If the target file was missing, it will log a hidden request to /s.nl?search=empty for every page request. I'm not sure if Netsuite have changed something to do with this since 2016.2, as I'm sure there used to be…

Using GET, there are two issues - the server's max size and, in the case of client scripts, the browser's limit. In the latter case, Internet Explorer is the worst offender with a limit of around 2083 characters. Firefox and Chrome have significantly higher limits. If a script is handling any significant volume of data, it…

cr223309 are you using a GET request to fetch the restlet?

As a workaround, you can probably disable the standard add to cart functionality and replace it with jquery ajax posts to the shopping domain. The page which collects the data will be non-SSL, but the data will be passed to a secure endpoint, so transmission is secure.

We've just got access to 2017.1 and it's evident that implementation of https throughout should automatically have included Sitebuilder sites - but it appears that this functionality has been deliberately crippled, presumably as a means of forcing people to upgrade to SCA. I can understand a commercial company wanting to…

Hi Andrea, Have you seen anything official which confirms the above? The release notes say "release 2017.1 includes the ability to set up your shopping domain as secure". The domain set-up seems to be the same for Sitebuilder and SCA, so I would have expected the change to apply to both?

You might want to look at the release notes for 2017.1 before considering this (they're available on SuiteAnswers). They're provisional at the moment and more than a little open to different interpretation, but suggest that https throughout, single domain for site and checkout and SSL certificates from a wider range of…

Touchpoints are not supported in SSP2.0 as yet, so I can't see that it's practical to develop a real world commerce application at the moment. You can't mix SS1.0 and 2.0 code within an SSP, but I'd expect you to still be able to deploy two different SSPs in subfolders off the same path - so you could deploy a 2.0 SSP, but…

nlapiGetWebContainer().getShoppingSession() is a commerce API call in SSP applications. SS2.0 support in SSPs has only just been released in 2018.2 and is subject to quite a few caveats. Have you seen the 2018.2 release notes regarding this?

Depending on exactly what you're trying to alert, it may be easier to just use a saved search? If not, SS2.0 (straight out of David Smith's search export Chrome extension): var employeeSearchObj = search.create({ type: "employee", filters: [ ["role","anyof","3"] ], columns: [ search.createColumn({ name: "entityid", sort:…

There are a bunch of fields on site builder category records that can't be accessed with a script or search, and the entire record isn't in the record browser. It sure would be nice if we could. I'd definitely second that one. If it was accessible in 2.0, it'd be a sufficiently compelling reason for me to look more…

Is there a particular reason for doing this in a Suitelet? If not, you may be better off just adding another formula column to the saved search and linking to the result instead. If you need to go down the Suitelet route, how many results will the search produce at its most extreme maximum case?

Depending on the number of results, the simplest option may be to create a saved search which outputs the customer data, then create a suitelet which publishes this to a public URL as JSON. You should then be able to use the suitelet URL as the dataLocation for the Google Maps API. The advantage to doing it this way is…

I'd assume they're referring to SSL certificates? If so, it's not possible to secure the main store with https throughout using standard Netsuite Sitebuilder functionality (you can do it by using Cloudflare though). You can however have a secure checkout domain as a subdomain of their main site, which requires purchase of…