Error syncing email content from AEM to ۶Ƶ Campaign Classic
When attempting to sync email content from ۶Ƶ Experience Manager (AEM) into ۶Ƶ Campaign Classic, the system may fetch content from the parent AEM page instead of the intended duplicated page. This issue occurs specifically when a copy of an already published parent page is created and synced.
Description description
Description
Environment
Product: ۶Ƶ Experience Manager (AEM) Managed Services Support
Product Offering: AEM Sites, Campaign Classic
Version: v6.5.19
Issue/Symptoms
The synchronization process fails to reflect the updated content from a duplicated AEM page in ۶Ƶ Campaign Classic. Instead, it displays content from the original parent page. This behaviour persists even after creating and editing a copy of the parent template.
Resolution resolution
Resolution
To resolve this issue, follow these steps:
-
Verify Permissions for Service User:
Log in to CRX/DE and inspect permissions for campaign-property-modification-service.
Ensure that this service user has both read and modify rights on relevant content nodes.
-
Update ResourceType in Custom Email Template:
Check the resourceType configuration of your custom email template.
Update it to use
mcm/campaign/components/campaign_newsletterpage
instead of/libs/mcm/campaign/components/campaign_newsletterpage
-
Perform Synchronization Steps:
Create a new import on the campaign side.
Duplicate the desired AEM page (create a copy).
-
Before synchronizing data on the campaign side:
Navigate to the workflow where data is being synced.
Remove the delivery activity and re-add it using identical configurations.
Refresh data and re-test synchronization.
-
Test Using Out-of-the-Box Templates:
Perform synchronization using an out-of-the-box Campaign email template to confirm functionality with default settings.
-
Allow Time for Cleanup Processes:
After creating a copy of the parent template, leave it untouched for some time before editing or syncing. This allows background processes like “Clean up after copy” to be completed.
-
Re-Test Synchronization:
Sync both parent and copied templates separately, ensuring no overlap during synchronization attempts.
If these steps do not resolve your issue, consider raising a support ticket referencing this case or testing further with assistance from ۶Ƶ Support engineers.