https://netsuiteprofessionals.com logo
Join Slack
Powered by
Hi All, one of our customer hase received the mess...
# suitecommerce
m
Hi All, one of our customer hase received the message "SCEM: Additional Parameter Required for Shopper Access to Suitelet URLs" in the message describe the following "After receiving the SCEM update on October 23, 2024, if you are using extensions with your account, you should reactivate your extensions." Does anyone has received the SCEM update yet ? Which version has the fix? Thanks!
t
I just checked out NetSuite Instance and it does not appear we have gotten the update yet. Outside of checking the Update Bundles screen, I am not sure if there is any other way of knowing. I am hoping that they notify us when it get updated.
👍 2
r
@Steve Goldberg as per my understanding -- those using nlapiResolveUrl and url.resolveScript should not need this change?
I tested this functions esp nlapiResolveUrl (as it was not included in the previous NS notification) and can confirm the new parameter is added in the external url returned by the function.
Hi everyone, do we have an info on how the SC Bundles will be handled or updated given this change in Suitelet external URLs? Trying to look for any email communication or an SA article but not seeing anything yet.
s
I'm not concerned about SC bundles breaking because of this change. The point of the SCEM bundle update and requiring that you reactivate them is that none of the bundles should need to be updated for this change – the changes will take effect after the compilation process completes.
c
I am also wondering about this. We have updated the SCEM tool to 2024.2.0, which was released last week. However, after reactivating the site, the Suitelet calls coming from a front-end extension file do not have the new parameter appended to the URL. Is there an additional step? How is the SCEM tool meant to dynamically change the URL that is hardcoded in the extension? Thank you.
✅ 1
m
after the activation you will se the following function:
✅ 1
function getSuitelet(script, deploy) {
✅ 1
at the begining of the shopping_x.js, myaccount_x.js and checkout_x.js
c
Hi Martin, thanks for the reply. I assume these are the .js files located in the 'extensions' folder of the application root? I opened up a 'shopping_x.js' file, which shows it was modified today during the reactivation process, but the getSuitelet function is not present.
m
yes, you can check directly on the website for the request
✅ 1
s
Screenshot 2024-10-28 at 15.07.02.png
c
Thank you both for the details. Unfortunately, the file does not contain the function. Would there be any difference if the site were SCA?
m
@Cory we have another customer experiencing the same issue: after activation, the code did not update.
we have experience both, for one is working but for the other one no
Captura de pantalla 2024-10-28 a la(s) 12.13.02.png
I initially thought they hadn’t submitted any request, but they actually have, @Steve Goldberg do you have any input on this?
r
Okay thank you @Steve Goldberg -- so that means after SCEM update and reactivating extensions those SC Extensions using external urls in their client side model will be updated with the ns-at params?
c
@Martin I appreciate you sharing that with me. I'm going to go check on a few other sites that may be affected.
s
After activation, have you cleared the cache?
m
Yes, also tried with a different param in the t parameter
s
@Regorr Segarra Yes, they will request the correct URL
✅ 1
@Martin 😞
m
What is strange is that is working for other account, with the same bundle version
👀 1
r
Thank you @Steve Goldberg! I am trying to update in our demo site to test this.
The solution provider manages upgrades to this SuiteBundle, so you may not update it directly. When an upgrade is available, the solution provider will install the new version in your NetSuite account.
I am trying to update the SCEM version and I get this instead.
m
It's a managed bundle, NS should update the bundle, you can't do it manually
r
were all of your accounts get the update already? I am thinking tstdrvs were not yet updated?
s
It is possible that test drives have not been automatically updated, in which case, you will need to request updates
r
oh yeah! Thanks @Steve Goldberg!
I just updated our SCEM on a customer's sbx account and after activation, I do not see the new function... hmmm. I will try with other sbx accounts and a safe production account later today.
@Martin good day. How are your accounts that did not reflect the changes yesterday? I still don't see the new function in the accounts I did activation yesterday...
m
Hi @Regorr Segarra i didn't found any solution for that, i will try again today and let you know
r
Oh, I just updated another account now and I can confirm it's updated. It looks like the function will only be added if that domain has SC Extension that are using suitelets in their client side models.
m
I have an activation that has SC Extension, but still not adding the code
image.png
r
Thank you for checking Martin... @Steve Goldberg are there any advise from NS on what's the gameplan for this scenario we are experiencing? Today is already very critical since tomorrow is already the 30th.
s
Nope. Raise a support case I guess
r
Thank you Steve!
Okay so far, our sites that are using SC Extensions with client side models using suitelets are updated with the new suitelet related function.
m
Hi @Regorr Segarra, I have investigated a bit more this, as you mentioned the activation code has a conditional code to only add the patch if is necessary
✅ 1
Captura de pantalla 2024-10-29 a la(s) 17.29.24.png
The suitlet script that i'm seeing are from the function processQueues from the fallback logger
So in this cases the suitlet will only be called if the initialization of logger instance fails, which is not a common case but could potentially be an issue. I think that this calls will be fixed in future updates of the extensions, but nothing to really worry about now
✅ 1
r
Thank you Martin for the additional info! 👏
2 Views
Open in Slack
PreviousNext
Powered by