Jooeun Lee
Sep 9, 2015
  1787
(2 votes)

Asset Importer fix for EPiServer Commerce 8 and CMS 8

I recently helped a customer resolve this issue and will share the solution. The customer was developing on the latest versions of CMS and Commerce (i.e. version 8.X.Y). Breaking changes from CMS 7.X to CMS 8 prevented the Asset Importer from running in a set-up with Commerce and CMS 8.X.

In order to fix this, do the following:

  1. Update the Asset Importer project to match your Commerce site by installing NuGet packages.
  2. Get the fixes here.
  3. Run the tool as documented.

If you are interested in reading the details of the problem and the fix, go here.

If you need to solve this problem, I hope this helps. Please feel free to contact me with any questions/suggestions/bugs in EPiServer Expert Services by emailing me at jooeun.lee@episerver.com or by leaving a comment below.

Sep 09, 2015

Comments

Please login to comment.
Latest blogs
Integrating Optimizely DAM with Your Website

This article is the second in a series about integrating Optimizely DAM with websites. It discusses how to install the necessary package and code t...

Andrew Markham | Sep 28, 2024 | Syndicated blog

Opticon 2024 - highlights

I went to Opticon in Stockholm and here are my brief highlights based on the demos, presentations and roadmaps  Optimizely CMS SaaS will start to...

Daniel Ovaska | Sep 27, 2024

Required fields support in Optimizely Graph

It's been possible to have "required" properties (value must be entered) in the CMS for a long time. The required metadata haven't been reflected i...

Jonas Bergqvist | Sep 25, 2024

How to write a bespoke notification management system

Websites can be the perfect vehicle for notifying customers of important information quickly, whether it’s the latest offer, an operational message...

Nicole Drath | Sep 25, 2024