CMS 13 - DAM Asset Picker Showing Multiple CMP instances
In CMS 13 with CMP DAM integration, the DAM Library Picker currently prompts users to manually select a CMP instance when they have access to multiple instances. For users such as partners who frequently work across multiple instances, this creates unnecessary friction and interrupts the workflow.
The expected behavior is that CMS should automatically open or restrict the picker to a specific CMP instance based on its configuration, eliminating the need for manual selection. The DAM Library Picker already supports targeting specific instances (e.g., via instanceIds), but this capability is not currently utilized or exposed in the CMS integration.https://docs.developers.optimizely.com/content-marketing-platform/docs/library-picker#pass-options-in-url
A suitable resolution would be to enable CMS to pass and enforce a predefined instance through configuration or native support, or at minimum default to the last-used instance. This would streamline the user experience and align the integration with expected behavior.
Ali Raza Gilani
shared this idea