Sep 9, 2015
  2226
(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
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |