Content deployment issue

Question

Whenever I'm creating a headless content package by adding a filter by folder path, any update in the existing content is ignored during deployment. When I build and download the package in a lower environment, I can see the updated content is available. Even after uploading the package and downloading it in a higher environment, I can see the changes available. So it's confirmed that content is getting ignored during installation just because of the filtering content using the folder path. Has anyone noticed a similar behaviour? Wondering if it's a desirable behaviour? For any new content, it's getting deployed without any issue.

Here is the filter I have for the content package:

<filter root="/content/dam/reliant/en/oe/sign-up" mode="merge"/>

aanchal-sikka · Accepted Answer

@mukeshaem

Any content that already exists on the target environment, will not be updated due to mode="merge"

You would need to use update/replace instead. Please find the details below:

replace : This is the normal behavior. Existing content is replaced completely by the imported content, i.e. is overridden or deleted accordingly.
merge : Existing content is not modified, i.e. only new content is added and none is deleted or modified.
update : Existing content is updated, new content is added and none is deleted.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded