acs commons include not working in cloud

@sirishap9577191 Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

Hi @sirishap9577191,

If you're using acs-commons/granite/ui/components/include to include a reusable dialog field, and it's not visible in AEM as a Cloud Service, it's likely due to deprecation or incompatibility with AEMaaCS’s stricter Sling Model enforcement and validation.

Kindly refer to these step-by-step checklist to help you troubleshoot and fix it:

1. Use the Updated Include Path

Instead of using the deprecated ACS Commons component path:

acs-commons/granite/ui/components/include

Use this supported core component include:

Instead of using the deprecated ACS Commons component path:

<sling:include
    jcr:primaryType="nt:unstructured"
    resourceType="granite/ui/components/coral/foundation/include"
    path="/apps/your-project/components/dialog/reuse-field"
/>

The ACS Commons version is not always supported in AEM Cloud, but the official Granite foundation include works reliably.

2. Verify the Included Dialog Path

Make sure the included node exists and is structured correctly. For example:

/apps/your-project/components/dialog/reuse-field
    - jcr:primaryType = nt:unstructured
    - sling:resourceType = granite/ui/components/coral/foundation/form/textfield (or relevant type)
    - name = ./yourField
    - fieldLabel = Your Field

The included node must represent a valid form field component or container.

Note: 

The include component you're referring to is here: ACS Commons Include Component (GitHub)

• The component is old and hasn’t been updated for modern Coral 3-based dialogs

• No Cloud-specific validation support

This component was designed before AEMaaCS and doesn’t account for stricter validation/structure in AEM Cloud.

Adobe AEMaaCS Compatibility Guidance

In the AEMaaCS upgrade readiness docs:

• Custom Coral 2 or non-core components are often flagged as unsupported

• Adobe recommends using only core Granite resourceTypes for dialogs

“Use only supported Coral UI components and Granite APIs… avoid relying on older ACS Commons UI components.”

ACS Commons Cloud Compatibility Notes

In various issues and PRs, maintainers suggest not using UI-based ACS Commons features (like dialog includes) in AEMaaCS projects and favor core Sling/Granite equivalents.

Hope that helps!

Regards,
Santosh