Replace in Target content by Experience Fragment does not work for a product carousel | Community
Skip to main content
I
IngeSc
Level 2
January 15, 2021
Solved

Replace in Target content by Experience Fragment does not work for a product carousel

  • January 15, 2021
  • 1 reply
  • 1141 views

Hi everyone,

 

We are facing the following issue. We have set up Experience Fragment template and the IO integration AEM/Target. 

 

If we setup activities in Target and add or replace an element by Experience Fragment this works for simple components (e.g. image, text). However if we try to achieve the same using a component like product carousel the Experience Fragment does not get displayed ( the component is included in the XF template of course). So you can see it has been added but the space where it is added does not show the actual component (so it looks like an empty placeholder).  The experience fragment itself works fine so the issue occurs only if we try to use it in an activity via Target. 

 

Has anyone experienced the same issue?

 

Best regards 

 

Inga

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by josejr19

    When you say "we have set up the experience fragment template", is this a custom experience fragment template or the one out of the box? Can you also share more details on the component you are using, is it running specific functions at runtime to obtain product detail information and then placing it a list as an example?

     

    I think at face value what I am thinking is happening is you have a race issue between the js and the markup because of how Target parses the markup from an experience fragment and places it into the selector. 

     

    Hope this helps!

    1 reply

    J
    josejr19Accepted solution
    Level 5
    January 15, 2021

    When you say "we have set up the experience fragment template", is this a custom experience fragment template or the one out of the box? Can you also share more details on the component you are using, is it running specific functions at runtime to obtain product detail information and then placing it a list as an example?

     

    I think at face value what I am thinking is happening is you have a race issue between the js and the markup because of how Target parses the markup from an experience fragment and places it into the selector. 

     

    Hope this helps!

      Terms & ConditionsAccessibility statement

      Loading footer...