Expand my Community achievements bar.

SOLVED

Dynamic media asset (image) shared from remote dam to site author instance not working

Avatar

Level 1

Hi,

 

I have a use case where I have setup a remote dam (connected asset) instance, configured dynamic media on it. Then uploaded an image asset.

 

1. Now I want to use this asset in the author instance which is started with dynamic media.

2. I can see this asset in content finder when creating a page

3. I can author a dynamic media component on the page and drag-drop the asset fetched from remote dam

4. When I see the page in preview mode the image is getting displayed, but if I open the page in disabled mode or publish the page in a publisher, then the image asset is not visible.

 

Any one has come across this situation or have any idea. Please share

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @nirajk2 ,

 

Found this in the documentation - https://experienceleague.adobe.com/docs/experience-manager-65/assets/using/use-assets-across-connect...

 

ChitraMadan_0-1625176411166.png

You can view the status of asynchronous jobs from the Async Job Status dashboard at Global Navigation -> Tools -> Operations -> Jobs.

Please can you tell us if the image exists on publisher and still you are not able to see it.

 

Thanks,

Chitra

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi @nirajk2 ,

 

Found this in the documentation - https://experienceleague.adobe.com/docs/experience-manager-65/assets/using/use-assets-across-connect...

 

ChitraMadan_0-1625176411166.png

You can view the status of asynchronous jobs from the Async Job Status dashboard at Global Navigation -> Tools -> Operations -> Jobs.

Please can you tell us if the image exists on publisher and still you are not able to see it.

 

Thanks,

Chitra

Avatar

Level 6

What I have seen is, when you are in wcmmode edit, the image reference points to the local copy of image and when wcmmode is disabled it refers the dynamic media assets. May be you do not have the asset in your local and that is the reason you are not seeing it.