AEM Desktop App does not sync /content/dam/formsanddocuments despite Adobe documentation

[RajeshKi]

Hello Adobe Team,

We are using AEM Forms 6.5 LTS with the latest AEM Desktop App.

According to Adobe documentation for “AEM Desktop App for AEM Forms”, it states:
“On successful connection, the app populates the content/dam and content/dam/forms and documents folders.”

However, in our environment:
- /content/dam/assets syncs correctly to the Desktop App
- /content/dam/forms and documents does NOT appear or sync in the Desktop App
- Forms & Documents is visible and accessible in AEM UI and CRXDE
- Permissions on /content/dam/forms and documents are verified
- Restarting AEM Forms and Desktop App does not change the behavior

We would like confirmation on:
1. Whether Forms & Documents sync support has been deprecated in current versions of the AEM Desktop App, OR
2. If additional configuration is required beyond what is documented, OR
3. If the referenced documentation is outdated and needs correction.

Any clarification from Adobe would be greatly appreciated.

Thank you.

[Pranay_M]

Hi @RajeshKi,

Please find below the answers to your questions:

 

1. Has Forms & Documents sync support been deprecated in the current AEM Desktop App?

• No deprecation is documented.
• The dedicated AEM Forms + Desktop App article continues to document /content/dam/formsanddocuments as auto‑populated on connect, as of the latest publication in 2025
  (Adobe Experience Manager (AEM) desktop app for AEM Forms).

So from Adobe’s own official standpoint: this capability is still supported and expected to work for AEM 6.5 Forms. If it is not working in your environment, that points to a defect or configuration problem, not an intentional deprecation.

2. Is additional configuration required beyond what is documented?

The same article spells out the only “special” configuration on the Forms side:

1. Log into AEM Forms Author as admin.
2. Go to Tools → Deployment → Operations → Web Console.
3. Open FormsManager AddOn Configuration.
4. Uncheck Asynchronously Sync Resources.
5. Save and restart the AEM Forms server.

After that:

“After the restart, the AEM Forms Server is enabled to accept and share content with the AEM desktop app.”
— Adobe Experience Manager (AEM) desktop app for AEM Forms

There is no additional public configuration documented for:

• Adding /content/dam/formsanddocuments manually to some allow‑list, or
• Enabling a separate “Forms DAM” mount.

So, if:

• You are correctly using /content/dam/formsanddocuments (note: no spaces, different from /content/dam/forms and documents); and
• FormsManager AddOn Configuration is set as above; and
• You have restarted after changing it; and
• Permissions for your AEM user cover both /content/dam and /content/dam/formsanddocuments;

then from a docs standpoint you should be fully configured. One thing to double‑check is the exact path name:

• Official Forms path the Desktop App expects: **/content/dam/formsanddocuments**
• Customer‑created / Forms Portal paths are sometimes named with spaces (/content/dam/forms and documents).

3. Is the documentation outdated and in need of correction?

Given:

• The article was updated March 2025 and still explicitly promises /content/dam/formsanddocuments sync, and
• There is no opposing deprecation or removal note in the LTS release notes,

The current view within Adobe is that the documentation remains accurate and the feature is supported.

If in practice the latest Desktop App no longer mounts Forms content on any 6.5 instance, that would indicate either:

• A regression in the Desktop App or
• An undocumented behavior change on the Forms side.

Thanks
Pranay

1.