Can Asset Selector (PureJS) Show Folder Structure in Delivery Environment?

[olsalas711]

Hi community,

We’re using the PureJS Asset Selector (assets-selectors.js) with IMS authentication in a delivery environment (delivery-pXXXXX-eXXXXXX.adobeaemcloud.com). Our setup is working well, and we’re successfully filtering assets (e.g., by dam:assetStatus).

However, we would like to know:

Is it possible to display the folder structure (i.e., hierarchy of /content/dam/...) within the Asset Selector UI when used in a delivery environment?

Currently, the selector opens with the “All Assets” view, and no folder navigation is shown, even though we can confirm that assets are organized into folders in the author repository.

Implementation context:

Authentication: IMS Flow with PureJSSelectors.registerAssetsSelectorsAuthService

Selector: PureJSSelectors.renderAssetSelectorWithAuthFlow

Props passed:

repositoryId: "delivery-pXXXX-eXXXX.adobeaemcloud.com",
aemTierType: '[1: "delivery"]',
filterFormProps: {
  "dam:assetStatus": ["approved"]
}

Questions:

1. Is the folder navigation (e.g., “Show Folders” toggle) supported when the selector is used in delivery environments?
2. If so, is there a flag or configuration I need to enable to allow the folder structure to be displayed?
3. If not supported, is this a current limitation of the delivery tier?

Any guidance or workarounds would be appreciated. I'm happy to share more code or screenshots if needed.

Thanks in advance!

[shubhanshu_singh · Accepted solution]

Hi @olsalas711 Folder Structure is available on the author layer but not on delivery for Asset Selector.
If you are using Dynamic Media Open API, the URL of the asset depends solely on the UUID of asset rather than the folder structure.

If you still want to see folder structure, you can select source as author repo and apply filter on status=approved. This way you will be able to see a tree hierarchy for approved assets.

[kautuk_sahni]

@olsalas711 Did you find the suggestion helpful? If you need more information, please let us know. If a response resolved your issue, kindly mark it as correct to help others in the future. Alternatively, if you discovered a solution on your own, we'd appreciate it if you could share it with the community. Thank you.