Sometimes it's the little things isn't it? Ha! That's probably it. I'll update my comment once I've completed trying that.
Edit:
Hey Sam,
Just wanted to report back, the yarn msdyn365 command seemed to be the missing link. We now have Adventure Works deployed again. Thank you so much for taking the time to respond, and we look forward to the 10.0.25 release.
Are you using "yarn msdyn365 pack" it should generate a zip file not a .tgz.
I think that's the issue.
hope that helps,
Sam
Hi Sam,
Thanks for the reply.
We are currently on the most up to date SDK. We have run yarn recently as well.
The error I was getting during validation was:
Validation status
Invalid - The package cannot be extracted
Here are the pack results:
yarn pack v1.22.17
success Wrote tarball to "C:\\repos\\Msdyn365.Commerce.Online\\Msdyn365.Commerce.Online-v1.0.0.tgz".
Done in 1.31s.
The file uploaded to the asset library was:
Msdyn365.Commerce.Online-v1.0.0.tgz
Here are the dependencies:
"dependencies": {
"@msdyn365-commerce-modules/fabrikam-design-kit": "9.34",
"@msdyn365-commerce-modules/msdyn365-exp-test-connector": "^1.0.0",
"@msdyn365-commerce-modules/starter-pack": "9.34",
"@msdyn365-commerce-theme/adventureworks-theme-kit": "9.34",
"@msdyn365-commerce/bootloader": "^1.0.0",
"@msdyn365-commerce/retail-proxy": "9.34",
"reactstrap": "^6.5.0",
"stack-trace": "^0.0.10",
"tslib": "^1.9.3",
"path-browserify": "1.0.1",
"stream-browserify": "3.0.0",
"browserify-fs": "1.0.0",
"util": "0.12.3",
"react-universal-component": "^4.0.0",
"@babel/runtime": "^7.12.5",
"run-script-webpack-plugin": "0.0.5",
"terser": "5.5.0",
"terser-webpack-plugin": "5.1.1",
"process": "0.11.10",
"sass-loader": "^10.2.0",
"css-loader": "^2.1.1",
"node-sass": "^6.0.1",
"mini-css-extract-plugin": "^0.5.0",
"css-minimizer-webpack-plugin": "3.1.3",
"ignore-emit-webpack-plugin": "2.0.6"
Steps taken prior to packing:
* We downloaded the 10.0.24 version from the Github repository
* Ran yarn in the folder from the VS Code Terminal once the folder containing all files was unzipped
* Ensured the .npmrc file was correct (followed the Install Adventure Works Theme documentation)
* Ensured the .yarnrc file was correct
* Ran yarn add @msdyn365-commerce-theme/adventureworks-theme-kit@9.34
* Added font files to \public\webfonts
* Added resource folder to \public\src
* Ran yarn start and checked localhost against our e-commerce site using ?theme=adventureworks
* The theme appeared to change our modules and theme style to that of adventure works
* Ran yarn pack
* Uploaded .tgz file
Hi Jritz,
What error are you seeing during validation, the usual error one may see is if the package was built with an older version of the SDK? To fix it's documented here.
Also, can you share your dependency section in your package.json file?
Does it look similar to this:
"dependencies": {
"@msdyn365-commerce-modules/fabrikam-design-kit": "9.34",
"@msdyn365-commerce-modules/msdyn365-exp-test-connector": "^1.0.0",
"@msdyn365-commerce-modules/starter-pack": "9.34",
"@msdyn365-commerce-theme/adventureworks-theme-kit": "9.34",
"@msdyn365-commerce/bootloader": "^1.0.0",
"@msdyn365-commerce/retail-proxy": "9.34",
"reactstrap": "^6.5.0",
"stack-trace": "^0.0.10",
"tslib": "^1.9.3"
},
Have you run "yarn" recently to ensure you have the latest packages before the build of "yarn msdyn3656 pack"? And it's good to run "yarn msdyn365 update-versions sdk" to force update of the SDK.
To make this easier, I'm working on creating a package for 10.0.25 that will include the AW theme, so future updates you won't need to build yourself. I hope to have that published by the end of this week to LCS global assets.
thanks,
Sam
Hi Sam,
Strangely enough, we did not have any extensions applied prior to applying the global extension update, yet we did have Adventure Works as an available theme for selection. I'm working on the process now of adding Adventure Works to the SDK, packaging that up, and uploading to LCS (though I must say, the documentation could be a bit more concise). As it stands now, I have followed the documentation exactly for installing Adventure Works in the SDK, and when I use yarn pack to get the .tgz file, I cannot get it to validate when uploading to e-commerce asset library. Any insight as to steps I may be missing? It is the .tgz file that we are to upload, correct?
Hi Jritz,
If you had previously deployed AW theme then that implies you had an e-commerce package extension installed and this update does not include the AW theme. So you'll want to create a new package with the AW theme added as you did originally but with updated 10.0.24 release. We are working on merging in the AW theme into our standard packages in shared assets and should be available for our next release.
thanks,
Sam
Good Afternoon,
We followed these steps to update our module library. We did not previously have any extension installed. We were running adventure works as the theme for one of our sites, but now adventure works isn't showing as an available theme on site builder at all for selection. Can you shed some light on this? We upgraded to 10.0.24 from 10.0.21.
Thanks for posting about this.
André Arnaud de Cal...
292,516
Super User 2025 Season 1
Martin Dráb
231,430
Most Valuable Professional
nmaenpaa
101,156