We got caught off-guard with the NetSuite (SCEM) notification "Starting October 30, 2024, the Shopper role’s access to the Suitelet’s external URL requires an additional parameter." We attempted to apply the fix via the following process: 1. Deactived the Extension causing the page not to load 2. Copied the External URL from the Suitelet in NetSuite UI ) which includes '&ns-at=VALUE' 3. Located the Extension scritp in NetSuite UI file cabinet making the call to Suitelet & overwrote the internl URL with the External URL from step 2 above 4. Reactived the Extension Result of above attempt to fix = CORS ERROR Attempt to fix the CORS error by applying the follwing to the Suitelet:

// Add CORS headers
                context.response.addHeader({
                    name: 'Access-Control-Allow-Origin',
                    value: '*'  // Or specify your SuiteCommerce domain
                });
                context.response.addHeader({
                    name: 'Access-Control-Allow-Methods',
                    value: 'GET'
                });
                context.response.addHeader({
                    name: 'Access-Control-Allow-Headers',
                    value: 'Content-Type'
                });

This did NOT work. Any suggestions?

Hi. Two things: 1. These are not the instructions that we sent out with the notice on how to resolve this issue. I will copy them below, but SCEM will automatically apply the relevant URL parameters so you don't need to do that. 2. You're not allowed to overwrite CORS headers, so you shouldn't try.

Thank you. Okay, all steps were completed including installing the newest version of the SCEM (2024.2.50). Still not working; hence, the additional measures.

When you inspect the processed extension JavaScript file for your site, do you see at the top the generator for the Suitelet URLs and your Suitelet URL with the correct parameters?

@Steve Goldberg Sorry. I haven't forgotten about this. I really need to be doing this fix in SandBox, but running into an issue when trying to setup a new domain in SandBox to get it operational; "*Record Not Saved* The store domain name you chose 'mysandbox.com' is already taken. Please go back and choose another." Trying to see if domain provider can help with this. Will continue thread once setup is complete, if you are still interested. ; )