Error message, "More than one image in the conversion array for image xxxxx" in EngageOne Designer

Product Feature: Build/Publish

Issue

HIP generation fails with following error:
 
More than one image is in the conversion array for image "S1XXXXXX.Fxx"

Cause

This could be caused when more than one input image is mapped to the same output image name, for example:

image1.jpg mapped to S1G0004J.F10
image2.bmp mapped to S1G0004J.F10

 

Resolution

UPDATED: October 18, 2019
Check the resource map for the device being used in the production job to ensure there are no instances where multiple input images are mapped to the same output image name. This can easily be done by sorting using the Output Datastream Resource column. If there are any duplicates and the Default Resource Map is being used, a User Defined Resource Map will need to be created (it is not possible to edit the Default Resource Map), where the images that are mapped to the same output image must be defined with unique output names. Confirm that the name assigned does not clash with any of the output names defined in the Default Resource Map. While HIP generation, if the output device is specifically mapped to a user-defined resource map, any entries that are not in this map will be picked up from the Default Resource Map. If all of the resources are defined in the user-defined resource map, there is no need to validate whether the names are unique compared to the Default Resource Map. 

If this doesn't resolve the issue, the image(s) in question may be available in the Hive in the Local Cache, if so, these can be downloaded, give a new name, and redeployed.

If this doesn't resolve the issue, the user may need to clear the local cache. Refer Clearing local file cache in EngageOne Designer