Solution Import Error or Dataverse Error: Cannot start the requested operation [EntityCustomization] because there is another [PublishAll] running at this moment
Have you ever run into this error while trying to publish solution components, update web resources, apply field/entity customizations, or import a solution into your environment?
Frustrating, right?
Let’s break it down — why this happens and how you can fix it (or at least work around it).
Option 1: Before importing any solution, always check the solution history. See if there’s already a patch or update in progress. If there is, wait until it’s finished.
This simple check can save you from unnecessary failures during solution import.
Option 2: check if your power platform and dataverse is connected with F&O or Finance operations instance, then there should be some bug in some versions (10.0.44) and they already provided bug fix as quality update in LCS, you can update that accordingly
One of the issue referred as – VRMContactPersonEntity causing issue in virtual entities data sync. Problem is due to obsolete property on the virtual entities, there is a problem with syncing the to Dataverse.
Workaround: Apply the hotfix from the LCS and then try to do virtual enitity refresh.
