What if product managers wants to have all images tagged in InRiver, but does not really like to do it manually? How can that be automated using artificial intelligence in the cloud? In this blog post I create a new InRiver iPMC extension that integrates to Azure's Computer Vision API.
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 messages about system events with each other. At the moment, EPiServer supplies four event providers. This post is about implementing a new event provider, using Redis as a broker for these event messages.