How to render the content fragemnet data on page in AEM using sling model

@anilkumar9 

What is the exact issue you are facing with above code?

You can refer to this blog post, it might help 🙂

https://aem4beginner.blogspot.com/fetch-content-fragment-using-sling-model

Hi @anilkumar9

After fetching the fragment data, you need to adapt to content fragment and iterate over the content elements like below.

private HashMap<String, Object> myObj = new HashMap<>();

ContentFragment fragment = fragmentResource.adaptTo(ContentFragment.class);
if (Objects.requireNonNull(fragment).getTemplate() != null
        && (fragment.getTemplate().getTitle()).equals(YOUR_CF_NAME)) {
    Iterator<ContentElement> elements = fragment.getElements();
    ContentElement element;
    while (elements.hasNext()) {
        element = elements.next();
        myObj.put(element.getName(), element.getValue().getValue());
    }
}

HI @anilkumar9 ,

Your Sling model looks generally well-structured for fetching data from a content fragment and rendering it on a page. However, there are a few things to consider and potentially adjust:

1. Ensure Correct Resource Path:

   • Verify that the fragmentPath field is correctly populated with the path to your content fragment. It seems you're expecting an array of paths, but if it's just one path, you might want to change the type from String[] to String.

2. Check Property Name:

   • Ensure that "data" is the correct property name within your content fragment to fetch the desired data. If you're unsure, you can check the property name in CRXDE Lite or the AEM Content Fragment editor.

3. Handle Data Retrieval:

   • If "data" is a complex property (like a JSON or XML structure), you might need to parse it accordingly to extract the specific data you want to render on the page. If it's a simple string, then your approach should work fine.

4. Error Handling:

   • Add proper error handling in case the content fragment path is not found or if the "data" property is missing or empty.

5. Rendering in Sightly/HTL:

   • Make sure you're correctly rendering the data in your Sightly/HTL component. If fragmentData is a complex structure, you might need to iterate through it or access its properties accordingly.

6. Debugging:

   • If the data is still not rendering as expected, consider adding log statements or using a debugger to inspect the values of fragmentPath and fragmentData during runtime to identify any issues.

7. Model Registration:

   • Ensure that your model is registered correctly and that the SampleGridImpl class is correctly referenced in the component's sling:resourceSuperType or via the cq:dialog of the component.

By addressing these points and possibly debugging further, you should be able to resolve any issues with fetching and rendering the content fragment data on your page.

Hi @anilkumar9 ,

Can u check if u are resourceResolver is not null? Are u getting any errors check in error logs.

@anilkumar9 Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!