https://netsuiteprofessionals.com logo
Join Slack
Powered by
I am getting this error when i try to active my th...
# suitecommerce
l
I am getting this error when i try to active my theme any idea what this means?
👀 1
b
I am too!!!
Are you using the dev tools 2023.2.1?
l
yes
b
I fixed the scss issues bc of the new dart sass library. Deployed the theme and when i tried to activate it i get that error.
l
lets wait for someone to respond - see if they can fix it
b
I have a NS support ticket but i have not heard back from them.
I will let you know if I find a solution.
l
👍
b
Is this the error you're getting?
Copy code
{
  "type": "error.SuiteScriptError",
  "name": "79749",
  "message": "Compiler was unable to compile the given input file.",
  "id": null,
  "stack": [
    "createError(N/error)"
  ],
  "cause": {
    "message": "Compiler was unable to compile the given input file.",
    "stack": [
      "createError(N/error)",
      "map(/SuiteBundles/Bundle 500777/ExtensionMechanism.Server/CompilersMapReduce/SassCompilerMapReduce.js:165)"
    ],
    "name": "79749",
    "data": {
      "response": null,
      "notifications": []
    }
  },
  "notifyOff": false,
  "userFacing": true
}
l
yeap
b
Ok.
l
started happening right after our account was upgraded to 2024.1
b
Prolly same here. But we just got sandbox upgraded. We postponed the production upgrade until mid april.
l
then maybe its just a coincidence. but dont tell that to netsuite support. they get confused easily
b
I mean you upgraded prod right?
👍 1
So we did a refresh of SB and then upgraded to 2024.1
I am glad we did not do prod yet. Omg.
l
are you getting this error in sandbox?
b
Yes bc we upgraded sandbox to 2024.1
We held production upgrade until april 20th i think.
l
i guess they will fix it at some point.
b
I hope they are aware.
s
We’ve had a few cases about this already and they have all been because of incorrect Sass syntax
The full error message should give you details about which specific part of your code is not correct
l
we made no changes to Saas Syntax tho
s
Yes but we changed the Sass compiler
b
I did bc with the new dart library i had to change some values in some style sheets. But I fixed them and i successfully deployed the theme. The issue is when i try to activate it. I get the same error that Livio is getting.
s
You should have received a PFCN and see the help center updates that said we were changing from JSass to Dart
b
Livio run gulp check-dart-sass
l
i get several errors
b
Yes, so fix them based on the feedback you get in the console.
Then deploy the theme and try to activate it.
I did all that and i am getting the same error message when activating it. But the theme was successfully deployed with no errors of course.
l
what happens if i make a mistake and i deploy
b
It won’t let you deploy if there are errors
l
same error. and my changes didnt get deployed
b
Run gulp check sass
Or something like that command
Then fix your theme files and then run the theme deploy command
l
i fixed the theme files.
and i deployed without any errors, but activation is failing
b
Nice!
Which dev tools are you using?
2023.2.1?
I got an email from NS asking if I had 2023.2.2 I don’t even have that update available.
s
same case here: I ran gulp check-dart-sass. I can see a lot of errors. I will try to fix them and update this thread. 🤕
😞 1
b
Do you have the SCEM 2023.2.2 available?
s
no, not available to me, too. Good thing, I am developing in Sandbox. NetSuite should take a look on this and apply or at least notify all SCA/SC Customers. Update to the fixes: It reactivated successfully after fixing the errors found.
b
I started a support case and they said that i need to upgrade my SCEM to 2023.2.2 I dont have that even available.
s
Better yet, fix the scss errors then
b
Can you activate it?
✅ 1
I am getting the error: {"type":"error.SuiteScriptError","name":"79749","message":"Compiler was unable to compile the given input file.","id":null,"stack":["createError(N/error)"],"cause":{"message":"Compiler was unable to compile the given input file.","stack":["createError(N/error)","map(/SuiteBundles/Bundle 500777/ExtensionMechanism.Server/CompilersMapReduce/SassCompilerMapReduce.js:165)"],"name":"79749","data":{"response":null,"notifications":[]}},"notifyOff":false,"userFacing":true}
s
what command dd you ran?
b
gulp theme:deploy
I can deploy it with no errors
But when i try to activate i get the error above.
@suiteExperimenter @Livio So i checked the dart-sass compatibility, no errors. Deployed and no errors. When i tried to activate i am getting a new error in the impact changes instead of getting the error in the sass compiler. • {"type":"error.SuiteScriptError","name":"80253","message":"file.load: Missing a required argument: id","id":null,"stack":["createError(N/error)"],"cause":{"message":"file.load: Missing a required argument: id","stack":["createError(N/error)","loadFile(/SuiteBundles/Bundle 500777/ExtensionMechanism.Server/Services/FileApiSS2.js:41)","manageConcatWith(/SuiteBundles/Bundle 500777/ExtensionMechanism.Server/JobToProcess/ImpactChangesMapReduce.js:299)","map(/SuiteBundles/Bundle 500777/ExtensionMechanism.Server/JobToProcess/ImpactChangesMapReduce.js:228)","createError(N/error)"],"name":"80253"},"notifyOff":false,"userFacing":true}
s
try to deactivate all extensions and just activate the theme. then, check extensions one by one.
sorry I take it back.
It looks like it has something to do with SC ExtMech Impact Changes Map Reduce
✅ 1
I might file a case about this
you?
I reproduced your error what I tried to changed the version number of my extension
😵😞
b
Ok soooooo this is so weird i activated the theme after getting that error in the impact changes and the theme was successfully activated!!! I did not do anything tho. So something was changed behind the scenes.
Then I continued with the extensions and I fetched them correctly.
Will start testing dart stuff in each extension we have.
I could activate! So weird it just happened without any updates i know of from NS.
s
Looks like a defect but was fixed right away. I tried the Base theme without extensions, there was an error. I will try again and hopefully it will be fixed on my end as well.
🙌 1
9 Views
Open in Slack
PreviousNext
Powered by