Metadata schema is not matching in classic UI with touch UI

[sgreddy]

Hello,
I have applied the new metadata schema to a folder and it looks good in touchUI but when it comes to the classicUI for the same asset it's still picking the old assets, our marketing team is kind of new and flexible with classicUI it may take time for them to migrate to touchUI how can i fix this? Could you assist.
v6.5.18

[SantoshSai]

Hi @sgreddy,

That the know issue and I have experienced it before:
Touch UI metadata schemas (via the Metadata Schema Editor) do not directly reflect in Classic UI (Asset Editor). They use different mechanisms for rendering asset metadata forms:

Understanding the discrepancy

• Touch UI uses /conf/global/settings/dam/adminui-extension/metadataschema/ for metadata schema forms.

• Classic UI relies on legacy dialogs located under /apps/dam/content/asseteditors or /apps/dam/content/metadataeditors.

This means updating the schema in Touch UI does not update the Classic UI dialog automatically.

I would recommend to force users to use Touch UI (recommended long-term) or Update Classic UI dialog manually to reflect the new metadata fields.

Hope that helps!

[sgreddy]

Thanks @SantoshSai 

[AmitVishwakarma]

Hi @sgreddy ,

This happens because Touch UI and Classic UI use different mechanisms for rendering metadata forms.

Root Cause
In AEM 6.5:
Touch UI metadata comes from:

/conf/global/settings/dam/adminui-extension/metadataschema/<your-schema>

Classic UI metadata comes from:

/apps/dam/content/metadataeditors/<schema>.xml

So, updating the schema in Touch UI does NOT impact Classic UI unless you manually replicate those fields into the Classic UI XML-based dialog.

Solution:

Option 1: Update Classic UI Dialog to Match Touch UI Schema

If your marketing team still depends on Classic UI, this is your fix.

Steps:

1. Locate the Classic UI metadata editor node:

/apps/dam/content/metadataeditors/<your-custom-schema>.xml

If it's not there, copy the default:

/libs/dam/content/metadataeditors/default.xml -> /apps/dam/content/metadataeditors/customschema.xml

2. Edit the XML dialog manually:

Use CRXDE Lite or your IDE to open:

/apps/dam/content/metadataeditors/customschema.xml

Update it to include the new fields you added in the Touch UI schema.

Example snippet:

<textfield
    jcr:primaryType="nt:unstructured"
    fieldLabel="Campaign ID"
    name="./campaignId"
    xtype="textfield"/>

Repeat for all new fields.

3. Configure folder to use the custom schema in Classic UI:

Make sure your folder metadata schema selection (via /conf/... in Touch UI) matches the schema name in /apps/dam/content/metadataeditors/. If your Touch UI schema is named marketing-assets, your Classic UI dialog should be:

/apps/dam/content/metadataeditors/marketing-assets.xml

4. Clear Dispatcher & Browser Cache (if any)

Classic UI can cache XML dialogs heavily, so make sure to:

  - Clear dispatcher cache (if applicable)

  - Do a hard reload (Ctrl+Shift+R)

Option 2: Force Redirect to Touch UI

If Classic UI usage is temporary and you're okay pushing users to Touch UI:

Set the following config in:
/apps/dam/gui/content/assets/jcr:content

Add or modify:

{
  "cq:redirectTarget": "/assets.html",
  "sling:redirect": "302"
}

This can force Classic UI views (like /dam.html) to redirect to /assets.html, which is Touch UI.

Regards,
Amit

[sgreddy]

Thanks for the detailed info @AmitVishwakarma 
We have decided to go matching the required fields with classic vs touch.