Hi All, Has anyone experienced a "Cannot call method \"split\" of undefined" error under "Impact Changes" when trying to activate the domain? Sandbox and release preview accounts activate with no issues, yet production account produces this error upon activation.

Type the error into the search box 🙂 But yes, it is issue 754212 if you want to raise a case. We are working on it.

Our case has been assigned to the defect. The date I have been given for the fix is 19th March. Thought I would try my luck on here, due to a number of SCA projects now on hold ☹️

Oh, that sucks. Well, I can see that the team are actively working on it

@GWilliams try using an older Dev Extension Tools. @Steve Goldberg out of curiosity, Does the SuiteCommerce Team work on fixes once they are identified on their end? Or do they need a minimum amount of open cases to do this? I ask this since I have noticed several times that Suitecommerce team is aware of issues on activations, theme, core, etc and with luck we get a fix in the next release or very late but not in an acceptable period of time. In the meantime the agencies/developers always need to look for workarounds. For example for this current issue, I'm not aware of any suggestion to activate from NetSuite Team. This is just a constructive feedback.

Prioritisation is the same throughout all of NetSuite: we take into account the business impact and the number of customers affected. It is true that if more customers are affected then it increases the likelihood that it will be prioritised sooner. I’m sorry that you feel like the fixes aren’t coming quick enough for you.

Thanks for your reply. I bet I'm not the only one with this feeling.

@eminero are you using older dev tools with 2023.2.0 Extension management or reinstalling the older bundle itself?

You do not need to reinstall any bundle (it would not allow you, I think). Just try with a lower version of your Extension Dev Tools.

will do. thanks

@eminero I believe If it is a suitecommerce standard we cannot downgrade it right? Since it is a managed bundle?

@Charan you do not need to touch the bundle, I'm referring to the extension dev tools you download and use locally (you might have an older version already downloaded or in your repo)

I think the latest version works perfectly in the local but the issue during activating extension manager.