Exporting XF to Adobe Target - HTML XF gives issue - PageModel cannot be correctly instantiated by the Use API | Community
Skip to main content
Rohan_Garg
Community Advisor
Rohan_GargCommunity Advisor
Community Advisor
May 13, 2025
Solved

Exporting XF to Adobe Target - HTML XF gives issue - PageModel cannot be correctly instantiated by the Use API

  • May 13, 2025
  • 1 reply
  • 408 views

Hi All,


We are exporting and updating XF to Adobe Target. The cloud configuration is working correctly as expected.
However, when we export it as HTML XF, we get the below error in Target for rendering - 
<head><title>500 org.apache.sling.scripting.sightly.SightlyException: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.scripting.sightly.SightlyException: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.scripting.sightly.SightlyException: Identifier ca.projectX.core.models.PageModel cannot be correctly instantiated by the Use API</title></head>
<body> <h1>org.apache.sling.scripting.sightly.SightlyException: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.scripting.sightly.SightlyException: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.scripting.sightly.SightlyException: Identifier ca.projectX.core.models.PageModel cannot be correctly instantiated by the Use API</h1> <p>Cannot serve request to /content/experience-fragments/projectX/test-xf-12/test-xf-12.nocloudconfigs.atoffer.html on this server</p>

@preetpal_bindra - I saw your reply to the other question at Exported Experience Fragment not working in Target
Here are the details for the same - 

  1. All XF of type HTML are having this issue while the JSON export works correctly.
  2. We are setting up the Target for the first time.
  3. This is an AEM Cloud setup.

We are already having the node /content/experience-fragments/projectX/test-xf/test-xf.noloudconfigs.atoffer present to remove the clientlibs from XF when exporting to Target.

Any further steps to help troubleshoot?
@gokul_agiwal, @alexbishop  

 

Best Regards,

Rohan Garg

 

Best answer by Rohan_Garg

The root cause is that Adobe Target cannot execute AEM backend Sling Models referenced in your exported HTML because Target only renders static HTML or client-side JavaScript
The fix for this involved using the "noloudconfigs" to exclude backend-dependent scripts.

We validated the export URL /content/experience-fragments/projectX/test-xf/test-xf.noloudconfigs.atoffer.html is stripped of backend dependencies.

1 reply

Rohan_Garg
Community Advisor
Rohan_GargCommunity AdvisorAuthorAccepted solution
Community Advisor
August 20, 2025

The root cause is that Adobe Target cannot execute AEM backend Sling Models referenced in your exported HTML because Target only renders static HTML or client-side JavaScript
The fix for this involved using the "noloudconfigs" to exclude backend-dependent scripts.

We validated the export URL /content/experience-fragments/projectX/test-xf/test-xf.noloudconfigs.atoffer.html is stripped of backend dependencies.

Terms & ConditionsAccessibility statement

Loading footer...