Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Experience Fragment(XF) live-copy variation export to target removes original XF from target

sawan051
Level 3
Level 3

Hello Everyone,

 

I am working on Adobe target setup and export experience fragment to Target, I am on AEM 6.5.6.

Observed few issues:

1. If we create variation of XF as "live-copy" and export that to target, it removes original (previously already exported) fragment from Target and adds this new one. 

Expectation was to treat this as a new variation in target so that old and new both can be used by authors.

 

2. I have correctly configured externalizer domain with something like "https://abc.xyz.com", but the links and clientlibs inclusion on Target side shows publisher URLs in offer HTML. It worked fine for a while on 6.5.3, not sure if SP-6 has introduced this issue.

 

Please let me know if anyone has faced similar issue.

 

Thanks in Advance !!

Experience Fragments Target
1 Accepted Solution
Bhuwan_B
Correct answer by
Community Advisor
Community Advisor

Please check below documentation once. Also SP 7 is getting released tomorrow, you can install and try if the issue you are facing is due to Service Pack upgrade or not.

 

Bhuwan_B_0-1606284056860.png

 

https://experienceleague.adobe.com/docs/experience-manager-65/administering/integration/experience-f...

 

 

View solution in original post

2 Replies
Bhuwan_B
Correct answer by
Community Advisor
Community Advisor

Please check below documentation once. Also SP 7 is getting released tomorrow, you can install and try if the issue you are facing is due to Service Pack upgrade or not.

 

Bhuwan_B_0-1606284056860.png

 

https://experienceleague.adobe.com/docs/experience-manager-65/administering/integration/experience-f...

 

 

View solution in original post

sawan051
Level 3
Level 3

Thanks @Bhuwan_B, I can wait for next release. But I am not sure if SP6 has caused #issue-2, I wanted to know if anyone else in the forum faced similar issue.

 

Also the #Issue-1 never worked as I expected, that seems OOTB. But still I wanted to make sure if I missed any configuration or anything else.