Custom asset picker (3rd party) for universal editor | Community
Skip to main content
Level 1
October 6, 2025
Question

Custom asset picker (3rd party) for universal editor

  • October 6, 2025
  • 2 replies
  • 166 views

Hello Everyone,
Can anyone please guide me or share some documentation to integrate a 3rd party DAM (Frontify) in universal editor so the author can pick assets directly from "Frontify asset picker" and then the selected asset's URL is stored in my universal editor input box?

2 replies

AmitVishwakarma
Community Advisor
Community Advisor
March 5, 2026

Hi ​@KushalAs ,

There is no out‑of‑the‑box Frontify integration in the Universal Editor; you need to build a small UI extension that wraps the Frontify picker.
Pattern that works today:

  • In your model (component-models.json / CF model) use a field mapped to a string or JSON (e.g. UE text component, or a custom data type) where you want to store the Frontify asset URL/metadata.
  • Implement a Universal Editor extension (App Builder) that overrides the renderer for that field:
    • render a “Choose from Frontify” button,
    • open the Frontify Finder picker,
    • on selection, write the chosen asset’s URL (and any needed metadata) back into that field.
  • Do not override the built‑in media / reference item type for CF asset fields: those are validated as AEM asset references on publish, and remote assets (Frontify) will fail validation, so overriding text (or a custom data type that stores JSON) is the correct approach.

For implementation details, use these as starting points:

Extending the Universal Editor – overview of UI extension and custom data‑type renderers https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/extending

Configurable Asset Picker – reference implementation of an asset picker extension (you’d swap its AEM/Polaris backend for Frontify) https://developer.adobe.com/uix/docs/extension-manager/extension-developed-by-adobe/configurable-asset-picker/

Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
KushalAsAuthor
Level 1
March 6, 2026

@AmitVishwakarma Thank you for the solution approach. However I have used a similar approach and I was already able to achieve this. Thanks a lot! I appreciate it!

AmitVishwakarma
Community Advisor
Community Advisor
March 6, 2026

@KushalAs Glad to hear that it worked for you!  If the approach looks correct and aligns with what you implemented, you can also click on "Mark as Best Answer" so it can help others in the community who might face a similar issue in the future.

Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME