Hi,

I am not sure about the version that you upgraded and downgraded. You said that you upgraded from 13 to 14.21 and Soft Detete Convention is broken. When you downgraded from 14.21 to 14.20 then it works again? Or you downgraded from 14.21 to 13?

When we downgraded from 14.21 to 14.20 then it works again.

Unfortunately, I think it is best way to replacing your soft-delete convention by using new Archive feature. Because the new Archive feature from 14.21 and higher is same as soft-delete convention that you are doing. Using OOTB is also helpful for keeping your project to be able to continue to upgrade latest version with new OOTB features so far.

You can keep version 14.20 if you do want to fix your soft-delete convention in later version. But I think if you still have budget for that one then you can:

• Replace your soft-delete convention code by new archive code
• Migrate all data relates to soft-delete by Archive data

I have to disagree. The Archive is like a trash bin where the intention is to delete the trash at some point in time, ~30 days. We have business rules that allow products and variants to be soft deleted and then brought back in the future for various reasons. Our PIM internal Ids associated to assets and items remain the same, which is why we want to keep a soft delete convention.

Hi Mike,

The Archive is like to allow deletion temporary. If you do not want to clear trash bin automatically then you can turn off Archived Job interval

You also could change option for Archive threshold such as 90 days or longer as following:

services.Configure<CatalogOptions>(options => options.ArchivedThreshold = 90);