AEM assets integration

Was this article helpful?

Still need help? contact us



  • Hi, we were wondering if there was a way to migrate current data from binary assets in inRiver to linked files in AEM.

    We are currently working with a client that has thousands of resources in inRiver but is looking to migrate to AEM. We thought at first that matching entities (with the same file name) would simply be recreated / updated in inRiver, but it seems like we are receiving an error from the AEM extension.


    ERROR Error calling inRiver Aem Asset Service HTTP Status Code = 500

    2020-08-13 17:41:15.367 ERROR Body content - {"ClassName":"System.ServiceModel.FaultException`1[inRiver.Remoting.Faults.ArgumentFault]","Message":"Trying to add entity with unique field where the data already exists","Data":null,"InnerException":null,"HelpURL":null,"StackTraceString":"   at inRiver.Server.Repository.DataRepository.ValidateAddEntityFields(Entity entity)\r\n   at inRiver.Server.Repository.DataRepository.AddEntity(Entity entity)\r\n   at inRiver.AppService.ExternalAssetService.AemAssetService.addResource(String json)\r\n   at inRiver.AppService.ExternalAssetService.Controllers.AemAssetStorageController.Post(String environmentId)","RemoteStackTraceString":null,"RemoteStackIndex":0,"ExceptionMethod":"8\nValidateAddEntityFields\ninRiver.Server, Version=, Culture=neutral, PublicKeyToken=null\ninRiver.Server.Repository.DataRepository\nVoid ValidateAddEntityFields(inRiver.Remoting.Objects.Entity)","HResult":-2146233087,"Source":"inRiver.Server","WatsonBuckets":null,"code":[{}],"reason":[{}],"messageFault":null,"action":null,"detail":{"method":"AddEntity","argument":"ResourceFilename","message":"Trying to add entity with unique field where the data already exists"}}


    So our first guess was that the extension was trying to create an asset with the same unique FileName. We deleted the existing resource and everything worked.

    Now, we are wondering if there is a configuration we missed somewhere that allows us to keep existing resources but only fill the Aem related fields and let my resource entities live there or simply replace it automatically if it already exists in inRiver and recreate its links?

    The problem we have here is that we're going to have to delete all resources from inRiver before syncing from AEM. Are you planning on supporting this use case?

  • Avatar
    Joakim Larsson

    No, you have not missed a setting.
    The current suggested migration path is to download/export your images from inRiver, rename them following a relevant naming convention to apply linking, and then upload them to AEM Assets where you can synchronize them to inRiver. Read more here

    Adding support for Update and not only Forced Add sounds like a good suggestion for future functionality. It has not been planned into the adapter roadmap yet. Please add as a feature request and we will take your request into consideration.




Please sign in to leave a comment.