Wondering if anyone else has encountered an activation error “Impact Changes” after SC Bundles had been updated to SC 2020.2 when trying to activate just a theme (no extensions) based on SC 2019.2 theme code?

{
  "type": "error.SuiteScriptError",
  "name": "91663",
  "message": "Hash.update: Missing a required argument: options.input",
  "stack": [
    "createError(N/error)"
  ],
  "cause": {
    "message": "Hash.update: Missing a required argument: options.input",
    "stack": [
      "createError(N/error)",
      "getMD5Hash(/SuiteBundles/Bundle 343577/ExtensionMechanism.Server/Services/FileApiSS2.js:338)",
      "(/SuiteBundles/Bundle 343577/ExtensionMechanism.Server/Services/FileApiSS2.js:283)",
      "E(/SuiteBundles/Bundle 343577/third_parties/underscore.js:6)",
      "copyFiles(/SuiteBundles/Bundle 343577/ExtensionMechanism.Server/Services/FileApiSS2.js:267)",
      "copyTmpFile(/SuiteBundles/Bundle 343577/ExtensionMechanism.Server/JobToProcess/ImpactChangesMapReduce.js:349)",
      "map(/SuiteBundles/Bundle 343577/ExtensionMechanism.Server/JobToProcess/ImpactChangesMapReduce.js:218)",
      "createError(N/error)"
    ],
    "name": "91663"
  },
  "id": "",
  "notifyOff": false,
  "userFacing": true
}

You getting this error when deploying again or activating the already deployed theme based on 2019.2.x?

Both.. will explain. The website has both a live domain and a testing domain configured. After SC was updated to 2020.2, I had to make a simple adjustment to an extension. I then deployed the extension to the testing domain (without issue) and tried to activate. This is when I first encountered the error. At this time, I did not touch the theme. I then tried to activate the “live” domain and encountered the same error. At this point I verified that all extensions records had “_target_version_” populated correctly and each was populated correctly. Tried to activate again and encountered the same error. Next, using the test domain, I tried to ONLY active the default 2020.2 theme with no extensions and that worked. I then tried to activate 1 extension (the extension only adds a custom tab with values to the configuration) and the default 2020.2 theme, which failed. So I can activate the default 2020.2 theme, however if I add a simple extension that was previously deployed via 2019.2 tools, the activation fails. This is where I deployed the theme using the 2020.2 dev tools, only to fail trying to activate only the theme. Basically I cannot activate anything that was previously deployed using the 2019.2 tools. This is the only account that I have encountered this and we did file a case with NS… That case has gone cold.

I had the same issue with 20.1 theme/ext that I could not successfully activate together on 20.2

Assuming you still have the issue?

2019.2.x Ext Dev Tools is not compatible with 2020.2.x. You just need to update the gulp tool with target version set to >=20.2.0. Various things has changed in the new like now it has chunk-based uploading and deploy service changes and so on... I faced similar problem in 2 projects and the migration solved the issue. For already deployed stuff you need to change the target version json in the ext custom record then try activating again.

@Mohammad Sharaf Ali I did do exactly what you said and still have the issue.

Is fetch theme working in the new codebase?

No I didn't get a solution to the issue, ended up just migrating my theme to 20.2 theme.. just adding myself to the thread in case someone shares an actual answer

@Bryce The above mentioned solution worked for us. In one project we are using 2019.2 theme on 2020.1 bundle and in the other using 2020.1 on 2020.2 bundle.

We have this filed as a defect. Any specific instructions I can pass our SCA/Netsuite devs to resolve? Thanks! Defect 611835 SCA 2019.1.6 SCA Config 2020.1.0 SCA Ext Mgmt 2020.2.0

try removing the .tmp from your theme images

Thanks Flo… It was a combo of the .tmp and setting the target version to 20.2.0 for both the theme and theme extension custom record.

@Christopher Dembek Just tp quote, the second was already mentioned quite long before: For already deployed stuff you need to change the target version json in the ext custom record then try activating again. Glad to hear finally your problem is resolved 🙂