Just making sure you understand, I'm accessing these things from the clientside browser, not from extensibility APIs (which I just found out about today) or anything that has documentation I'm aware of. These are things you can get to by hitting F12 on your browser while in a SuiteCommerce page.

I also see another component which sounds like it's only available when the user is logged in, so maybe I could find out that way, and also find out their internalID: UserProfile The UserProfile component lets you retrieve information related to the user logged in to the SuiteCommerce website. You can get basic user…

@Donna Bernardo-Oracle Thank you for showing me that documentation. I see that the LoginRegisterPage extensibility component has events beforeLogin beforeRegister afterRegister but it doesn't have one for logout, so I would still not know if the user has been logged out or their session timed out, I would only know that…

I need to be able to get the Cart before the confirmation page, so the customer can see how much freight will cost before they order anything. If the Environment Component addTracker function only works on the confirmation page, that will not meet our needs. By getting the Cart with javascript running on the user's browser…

When I run a SuiteCommerce page with my 1.0 scriptable cart form level client script deployed, I find this error on the page: So I'm having doubts as to whether this API is available in SuiteCommerce Standard, or if it is, then whether it is available in Scriptable Cart form-level client script. If it's not available that…

Also, my scriptable cart form-level client script is written in SuiteScript 2.0, so I don't know if nlapi* functions work there. I'm unable to find out because log.debug does nothing or the logs it creates cannot be found anywhere that I know of. How else can I tell what a form-level client script is doing? The alert()…

@Sharon Grace Mendoza-Oracle I am responding to your question "Have you tried checking these SuiteAnswer articles: Commerce API and Shopping Objects?" I looked up those SuiteAnswers but I'm unable to use nlapiGetWebContainer() in either my scriptable cart form client script or my javascript that I inject onto every…

I had to do that loadJSON because SC.ENVIRONMENT.PROFILE is empty or null or undefined until then.

I was unable to reproduce the problem when the support agent contacted me, because it magically started working again. But then it broke again less than an hour later. What happened? The difference seems to be that in my failed attempt at reproduction of the problem, the variable that holds the secureString was assigned at…

I have replied to your email with the relevant and requested details. Thank you again.

Thank you very much; that's very kind of you!

Thank you everyone for your help! I solved the problem. This is how: I deleted the ns_npm_repository and gulp folders from my extension development folder. I re-unzipped the most recent extension development tools zip file into that folder and let it overwrite whatever was left. I ran npm install. I did the gulp…

I typed the whole case again today and got the same error: Case Not Created We're sorry, but a technical issue occurred while submitting your case and we weren't able to preserve your data. Please try resubmitting your case later or if it is urgent, call Support for further assistance.

Maybe I should try downloading the development kit again?

I'm not sure how to properly check some of these, but here's what I found out so far: SuiteCommerce Extension Management bundle version is 2022.2.1 SuiteCommerce bundle version is 2022.2.1 - we have SCS; we never installed or used SCA. Node version from typing "node -v" is v12.21.0 Gulp CLI version from typing "gulp -v" is…

Is Underscore not where the problem is happening?

I followed your instructions, but we don't have the Posh theme, we have the bridge theme, so the file I validated the JSON for is at: SuiteScripts : extensions : SC : com.netsuite.bridgetheme : BridgeThemeExtension@3.0.3 : Modules : WebFont : Configuration However, the JSON file at that location validated perfectly, and…

I am unable to submit a case through SuiteAnswers' online form, due to a "technical error" that occurs on submit, after having filled out all the questions. This happened twice including after logging back in and trying again.

We only have Basic Support. I am trying to get something working so our business can use it, but C1 and C2 issues sound like they're only for when the business is down because of the problem. Is it okay for me to submit a support case for when I cannot get something new to work, so that our business can move forward on…

yes, I can gulp extension:deploy successfully. This is what led to the Extension Manager crashing when it tried to re-activate Extensions. The underscore library seems to be what the errors in both gulp extension:deploy and the Extension Manager are about.

Oh no. When I re-activated the extension after gulp extension:deploy ing it, then it failed with this error in the Extension Manager. How do I fix THAT? {"type":"error.SuiteScriptError","name":"4647","message":"{\"message\":\"Missing comma in object literal\",\"fileName\":\"/SuiteBundles/Bundle…

Looks like running CMD as Administrator fixed the problem, and it seems to be allowing me to gulp extension:deploy now. However, when I ran gulp extension:deploy, I saw an error along the way. Should I be concerned about that? : [12:37:19] Starting 'do_validate'... SyntaxError: Unexpected string in JSON at position 18345…

Thank you for your advice and help so far. I went to Request Catcher and created a subdomain as you instructed. When my script sent the request, it appears that the secureString in the header is not getting parsed before the request is sent: GET /test?query=TestQuery HTTP/1.1 Host:…

I just deleted the API secret in Sandbox, and I get the same response, {}. This seems to mean that I get the same response for trying to use a non-existent API Secret, as I do for using an existing one (which I made sure was spelled exactly the same way in my SuiteScript, as it is spelled in the API Secret script ID).…

The Type of Registration is "required", which does enable Advanced Sign Up. However, the Domain type was NOT "Single Domain for Web Store and Checkout". So I deleted the domain (it cannot be changed to "Single Domain for Web Store and Checkout" once it's been created as another type), and created a new one for the same…