In InRiver some fields have raw values that need to be transformed because of a target system. It could be that all color codes should be consolidated to just 20 color groups. But how to do that? And where to store all the transformation combinations? In this blog post, I demonstrate how to implement an InRiver iPMC extension that transforms field values using a custom table in Azure Table Storage.

From working on InRiver PIM projects, I have implemented a few custom outbound connectors. They would export catalogs to EPiServer Commerce, Demandware (now Salesforce Commerce Cloud) as well as Azure Blob Storage. In this post I give away six tips on implementing a good outbound connector for InRiver Product Marketing Cloud (iPMC).

Digital marketers of today might want to work with dynamic product ads on platforms like Google and Facebook. This requires a machine readable product catalog file. To showcase how to make that data available, I created a tool for EPiServer Commerce, which generates and provides such a file.

When EPiServer runs in a load-balanced environment, the servers rely on exchanging event messages. EPiServer supplies four event providers. This post is about implementing a new event provider, using Redis as a broker for remote event messages.

I have heard a lot about Bitcoins and other cryptocurrencies. About what they are, what they can do and how much they will revolutionize payments and money transfers. So, as an experiment I decided to create an EPiServer Commerce plugin to accept payments in cryptocurrencies.

How can an AJAX service serve texts (error messages, label texts, product descriptions) or images from a multilingual EPiServer site? How to make sure that the server returns content in the correct language?

Read about a way to generically handle exceptions so they show a friendly error message to visitors, and a detailed stack trace to certain user groups.

When developing websites, sometimes adding extra attributes to certain HTML tags is needed. This is about how to do that dynamically on EPiServer properties, extending the Display Templates.

Imagine that you are developing a web platform (maybe even a SaaS product) to support multiple customers. It could be built as a multi-tenancy application, that offers a basic subscription and a variety of optional add-ons. How could authorization of access to each add-on be easily implemented?

I once did a big migration of an old Subversion (SVN) repository to a new Git repository, migrating all of the version history. This post is about how to do that.