This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

SuiteCommerce Advanced Developers: The 2019.1 release of the Extension Management Bundle includes the theme and extension developer tools for 2019.1 and 2018.2. If you are implementing the 2018.2 release of SCA, you must use the 2018.2 developer tools when creating themes and extensions due to non-backward compatibility.

Does this mean if you have a 2018 based theme and don’t want to update it to 2019, you’re stuck on SCA 2018.2?

Yesterday, I diff’d the SuiteCommerce Base theme  2018.1 and 2019.1.  There are 302 changed files and around 30 new files.  Yuck.  It’s unrealistic to update the theme files in reasonable timeframe.

Right now we’re copying over the new files in 2019.1 into a customized 2018.1 theme then fixing any errors that occur when trying to run in local development mode.

<@UD9EXR0MV>, what are NetSuite’s thoughts or plans on making SuiteCommerce Standard backward compatible?

By that I mean older theme versions will work without errors in newer versions of SC?

Yes, and that has been the way it has worked so far. There was an issue on SCEM 19.1 which basically was not considering backward compatibility with Themes based on previous versions.

if you have a support case open I can attach it to an issue record

<@UD9EXR0MV>, yesterday we had to stop using SCEM 2019.1 and go back to 2018.2.1 for local development.  I discovered a new problem where require.js was not loading the modules in the correct order when run from local dev mode.  I posted the specific issue that I ran into on the main suitecommerce channel yesterday.

I don’t have a case open for this issue.

it´s related to the differences betwee almond and require.js and how async works

please create a support case and I will attach it to the issue

I’ve had a similar problem with Kilimanjaro in the Modules/suitecommerce/CustomContentType@1.0.0/JavaScript/CustomContentType.Base.View.js  that only occurs in local development mode.  The CustomContentTypeBaseView.beforeInitialize.install() fails and I have to comment it out

<@UD9EXR0MV> we submitted two cases for these issues.  Case 3457341 covers the errors caused by the 2019.1 missing template files and case 3457760 for the require.js loading the extension views before the BackboneExtras module files.  NetSuite Support associated the case 3457341 with defect 542329 and case 3457760 with defect 544980. I also mentioned the Kilimanjaro local development issue with require.js loading in the second case.  If you have time, could check that the defects cover the issues mentioned in the cases?  I would appreciate it.  Thanks.

Yes, it does. The one with require.js is a bit more complex, the other will be out in the next e-fix