Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

Smart Crops reset after running DAM Update Asset Workflow

Avatar

Level 2

Hi,

 

I uploaded an image to my DAM and used it on a page with the default smart crops that AEM generated for my profile.

Now, I went back to DAM and changed some selection in the smart crop for one of my sizes where in for my small size smart crop I wanted to focus more on the object.

If now we run the DAM Update Asset Workflow again on the image, it resets what I had selected for my small size to the original one that was originally there?

Could someone please help?

 

Regards,

Ankush Dhingra

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@ankushd75501011 interesting but valid question.

 

As of I know, it is how it works.. since smart cropping works as part of scene7 process step in DAM asset update workflow. 

 

If you have to prevent below usecase, try to create separate workflow for scene7 sync with that single process step so that when image gets updated for general edits these smart crops will not refreshed.

 

Just option try it out but with this we will loose auto sync to scene7/DM , authors has to manually sync to scene7/DM whenever needed/ondemand.

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

@ankushd75501011 interesting but valid question.

 

As of I know, it is how it works.. since smart cropping works as part of scene7 process step in DAM asset update workflow. 

 

If you have to prevent below usecase, try to create separate workflow for scene7 sync with that single process step so that when image gets updated for general edits these smart crops will not refreshed.

 

Just option try it out but with this we will loose auto sync to scene7/DM , authors has to manually sync to scene7/DM whenever needed/ondemand.

Avatar

Level 2
I guess this should not be the behavior. If I have made changes to my smart crop, and when I run the DAM Update Asset Workflow which will eventually automatically run when there is a change in the metadata, the smart crop changes should sync in with the server rather than refreshing them ? Then I don't understand the use case of re usability here if eventually every time I can change a smart crop only after it has synced to the server and never run any workflow on it