Use different Webpart IDs from PnP Modern Search

[VerlindenEAM]

We are widely using PnP Modern Search within the organization and looking into Aequos.

What I understood is that Aequos is using the same Webpart ID's as PnP Modern Search.
Since we have too many sites and search implementation, we are not able to just move/migrate everything without too much downtime in the functionality.

Can this be changed so that it uses it's own Webpart ID's ?

[Laul0]

Hi @VerlindenEAM,

Thank you for asking us.
As you mentioned, having the same Web Part IDs allows switching from PnP Search to MDV without reconfiguring the pages and the environment.
This is volunteer behavior and we cannot change it because we will lose this possibility.
In other words, if you remove the PnP Search Package and replace it with the MDV one, it works! No additional action - just ensure the compatibility of the configuration and customizations before.

To check the compatibility, if your configurations are the same across your environment, you can create a Site Collection AppCatalog and deploy MDV on it. By default, the Site Collection AppCatalog is priority on the Tenant AppCatalog.

Hoping this answer will help you!

Best regards