https://netsuiteprofessionals.com logo
Join Slack
Powered by
Update from my prior note after review with NetSui...
# suitecommerce
r
Update from my prior note after review with NetSuite Support. The issue is the configuration as a whole isn't loading or more likely trying to load the wrong configuration record or not having the right key values to load the configuration record, hence all attributes are null. More investigation in process with NetSuite Support. This is impacting Shopping and not Checkout or MyAccount.
p
What version of SCA are you running?
I'm asking because the way to obtain the domain has changed significantly in oldish vs new versions
from:
Copy code
var domain = session.getSiteSettings(['touchpoints']).touchpoints.home.match(/^http(s?)\:\/\/([^\/?#]+)(?:[\/?#]|$)/i)[2];
to
Copy code
var effectiveDomain = config.domain || ModelsInit.session.getEffectiveShoppingDomain();
in this file: Modules/suitecommerce/SspLibraries@XXX/SuiteScript/Configuration.js
@Robert Samuels
r
@Pablo . client is on Elbrus.
@Pablo - issue occurred after 2020.1 upgrade and no issues with the SB still in 2019.2
p
Yup it might be a change in what the touchpoint returns
I'd give a try to session.getEffectiveShoppingDomain()
r
@Pablo - developer looking to what you mentioned specifically and adding some logs to determine the root cause .. THANK
@Pablo - also noticed that the certificates are showing "not loaded" in the domain tab but the site still loads as secure. Know there is a change with 2020.1 however, seems this screen also has a defect ?
p
Check the release notes for 20.1 there has been a significant change on Certificates and certificate handling.
In theory you have about 2 months to act on it before NS takes action.
Unfortunately I haven't got a 20.1 acct to play and comment further on that
r
Correct, they need to purchase new, however, that doesn't explain why the screen shows they aren't loaded when the old ones are still active ... OK if that's a nuance to the 2020.1 change I suppose, but will confuse customers
it is true that the new 2020.1 (May was deadline) aren't loaded which is maybe what the intent was .. ? just not clear
p
Indeed, it might be just bad UX only contemplating the new and not contemplating the old. But the new feature is very cool, specially for dev.
r
@Pablo - FYI efix scheduled for this week on the certificate UI issue
And .. unfortunately the method change above didn't fix the configuration record not loading issue ... defect has been filed or is in process
4 Views
Open in Slack
PreviousNext
Powered by