Fewer resources in episerver than in inriver?

This article explains why there are fewer resources in Episerver Commerce than in inriver.

Issue

You may have noticed that there are fewer resources in your Episerver Commerce solution than there are in inriver. Depending on your setup, specifically the image configuration and resource file naming, this may be by design.

Explanation

The resource files that are sent to Episerver Commerce can not have the same name as another resource file. Because of this restriction, if the Episerver Commerce Adapter processes a resource entity where the filename is the same as another one that was processed beforehand, it will be skipped and not sent to the Episerver Commerce Solution.

If a file has been skipped and not sent to Episerver Commerce you will find a warning logged in the inriver Control Center logs where it is specified what file was skipped.

Troubleshooting

Below you have will find some common causes as to why a file was skipped and not sent to Episerver Commerce.

Duplicate filenames

As mentioned in the explanation above, you can not send files with the same filename. If you see a log entry mentioning the file being skipped, you either have duplicate resource filename or Image Configurations which converts multiple different file types to the same type. 

• If there are resources with the same filename, you will need to rename or remove the resource entities until the filenames are unique.
• You should then set the FieldType "ResourceFileName" to Unique to prevent this from happening again.
  
  
  
  
• If you ensured that there are no resource entities with the same resource file name, you should also ensure that the image configuration is not the cause of the duplicates. The extension processes resource files AFTER they have been converted through the Image Configuration set in inriver Control Center.

Example

If you have an image configuration that sets two different resource files (picture1.jpeg and picture1.tiff) to a JPG format, the adapter will receive two resource files with the same name (picture1.jpg). This will result in one of the files being skipped.

Below is a screenshot of what the example looks like in inriver Control Center:

If a file is being skipped because of the image configuration, you need to remove one of the image configurations if you want both of the files sent to Episerver Commerce.

Further reading

How to use the episerver commerce adapter

Image configuration in inriver

inriver Control Center log