Virtual Happy Hour is canceled this month (March) due to Good Friday.
Virtual Happy Hour is canceled this month (March) due to Good Friday.
EPiServer.Commerce 9.0.0
EPiServer.Commerce 13.18.1
Mar 27, 2020
Jul 01, 2020
Core
Closed, Fixed and tested
Updating one catalog item (update only affecting meta data) invalidates these keys:
"EP:CV:NOLink"
"EP:ContentVersion:419__CatalogContent"
"EP:ECF:MO:419-9"
"EP:ECF:CDep:MO:9-419"
"EP:ECF:Version:?:"
"EP:ECF:Version:419"
"EP:ECF:Version:?:"
"EP:ECF:Version:419"
"EPLanguageData:419__CatalogContent"
"EPSegmentData:1073741832:sku-36127195__CatalogContent"
"EP:CV:NOLink"
"EP:ContentVersion:419__CatalogContent"
"EP:ECF:Version:?:"
"EP:ECF:Version:419"
"EP:ECF:Version:?:"
"EP:ECF:Version:419"
If the update also touches base entry data (not only the meta object), these invalidations are added:
"EP:ECF:E:419"
"EP:ECF:E:0"
"EP:ECF:E:*"
This seems very excessive, considering there are many duplicates. Most seem related to versioning, but there also seem to be two meta object keys invalidated that should be covered by one of them.
Of the version keys, other than being repeated multiple times, it seems that Commerce specific keys and general CMS keys that likely target the same (type of) dependencies are invalidated, e.g. "EP:ECF:Version:?:" vs "EP:CV:NOLink" and "EP:ECF:Version:419" vs "EP:ContentVersion:419__CatalogContent".
The CMS ones seem unnecessary. This is raised as CMS-15652.