After migrating to Acquia DAM module, Embed Entities not showing

My current workaround was reverting this deleted configs:

config/default/embed.button.acquia_dam.yml
config/default/entity_browser.browser.document_browser.yml
config/default/entity_browser.browser.media_browser.yml
config/default/entity_browser.browser.wysiwyg_acquia_dam_entity_browser.yml

Manually change the modules dependencies to remove the dependency on the media_acquiadam to set as media:

dependencies:
  module:
    - media

Run the config import and add a custom CSS to hide the Embed Media buttom from CKEditor to stop using it.

/**
* Hide the Acquia DAM button in CKEditor toolbar
*/
.cke_button.cke_button__acquia_dam {
display: none !important;
}

It would be great to have some information on how to properly handle the Entity Embed and Entity Browser and why they are not migrated during the process.

Hi rajeshreeputra,

I'm not sure how those were created as I'm not the first developer of the project, but by my testing shows that it was used together with the modules:
Entity Browser
Entity Embed

The entity browser was created using EntityBrowser widget from the Media AcquiaDAM module.
The Entity Embed after uses that EntityBrowser to allow insert media via CKEditor.

I will test the patch from nickolaj to see if solve the issue too.

nickolaj your patch only applies the workaround to remove media_acquiadam from the configuration. However, this does not restore Entity Browser or Entity Embed functionality.

The reason is that the Acquia DAM module no longer provides the required Entity Browser widget to support Entity Browser–based embeds. That widget exists only in the legacy Media Acquia DAM module. It appears that the Acquia DAM module has intentionally dropped support for Entity Browser in favor of using Drupal’s newer Media embed approach.

I’m fine proceeding with the patch as-is, as I can add CSS at the project level to hide the old Entity Embed button. However, for other projects, this change may cause confusion unless the behavior change is clearly documented and communicated, since Entity Browser–based embeds will no longer be available.