Quick question, the clients that have not received the last email notification about the extra

ns-at=netsuite_id

parameter on Internal Suitelet URL (effective from the next October 20th) should also review anything? That is not clear to me. @Steve Goldberg sorry to tagged you but I"m not sure who else might know about it.

I am also curious about this especially in regards to the NS bundled extensions. With this rollout, I see potential issues with suite-commerce extensions for SCA that refer to the suitelet URLs without the ns-at parameter. So will all these SCA extensions stop working after the 20th or is NetSuite planning to roll out new versions for these extensions with a fix, that can up updated via the extension manager? Here is a screen shot referencing the SC order status extension. Or is everything going to break like the permissions change rollout that we could not update any NS bundled extensions

That's an excellent point @Will Little I would like to know about that as well.

I wouldn't want to second guess the team that put together the list of affected accounts, so, @eminero, no?

@Steve Goldberg Backend and front-end side is affected.

Any update on this? Why we should only re-activate extensions? We need to update SC Extensions as well ? Thanks!

I just checked with the team – the re-activation is required after the SCEM update is pushed out because it will append the URL

ns-at

parameter to the Suitelet URLs for you. This means that we don't need to update the individual extensions themselves.

Thanks for the clarification!