Take the community feedback survey now.


Sep 9, 2015
  2037
(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
Meet the newest OMVPs – summer 2025 cohort

We’re excited to welcome the latest group of Optimizely Most Valuable Professionals (OMVPs) into the program! This summer’s cohort highlights a ble...

Satata Satez | Sep 5, 2025

The Sweet Spot: Hybrid Headless Architecture

When it comes to content management architecture, the pendulum often swings between tightly coupled “headed” CMS setups and the flexibility of full...

Minesh Shah (Netcel) | Sep 4, 2025

Preview Unpublished Pages and Blocks on the Frontend (Optimizely CMS 12)

Introduction In my previous post , I explained how to customize the ContentArea rendering pipeline in Optimizely CMS 12 so editors can see...

Adnan Zameer | Sep 4, 2025 |

How to automatically remove orphaned Opti jobs from the DB

Optimizely CMS provides a simple yet powerful built-in job system that handles most standard scheduling scenarios with ease. Developers can easily...

Stanisław Szołkowski | Sep 4, 2025 |