Dynamics Community Forum Thread Details

Publishing All Customizations Fails & Deployment Does Not Apply Changes in Dynamics 365

Hello everyone,

I am experiencing an issue with publishing all customizations in Dynamics 365 CRM (Dataverse). When I try to publish all customizations, I receive the following error:

"Publish failed: There is no active transaction. This error is usually caused by custom plug-ins that ignore errors from service calls and continue processing."

However, when I publish a single entity, it works without errors.

Additionally, when I deploy my solution, the deployment process completes without any errors, but the changes do not apply in the system.

What I Have Tried So Far:

- Checked dependencies in the solution → No dependencies are shown.
- Verified that there are no workflows, plug-ins, or third-party add-ins installed.
- Tried creating a new solution with nothing in it → Publishing still fails.
- Checked system jobs → "PublishAll" jobs fail with error code 80040251.
- Checked import history → Solution import completes successfully, but changes are not reflected.
- Used XRMToolBox "Dependency Identifier" → No major blocking dependencies found.
- Tried manually publishing components instead of "Publish All" → Works for single components but not for all customizations.

Environment Details:

Dynamics 365 CRM Online (Cloud)
Dataverse / PowerApps Model-Driven App
Solution Type: Unmanaged
No recent changes to security roles or permissions

Has anyone faced this issue before?

Why is "Publish All Customizations" failing, but single entities can be published?
Why does solution deployment complete successfully but not apply changes?
Is there a hidden setting or metadata corruption issue I should check?

Any help would be greatly appreciated!
Thanks in advance. 😊

Categories:

Microsoft Dynamics CRM

1. Check for Plug-in or Custom Code Issues

Even if no plug-ins appear active, some hidden or deactivated plug-ins could still interfere.
✅ Action Steps:

Open Power Platform Admin Center → Go to Solutions → Open the affected solution.
In the Plug-in Trace Log (Settings > System Jobs > Plug-in Trace Log), check for errors related to solution publishing.
If any plug-ins or custom workflow activities exist, disable them temporarily and retry publishing.

2. Verify Entity Metadata Integrity

Corrupt metadata in Dataverse can cause publishing failures.
✅ Action Steps:

Use XRMToolBox → Metadata Browser and verify if all entities are correctly retrieved.
Check if any recently modified entities have missing required attributes.
If a specific entity is problematic, remove it from the solution and retry publishing.

3. Perform a Manual Metadata Refresh

Dataverse may have an outdated metadata cache, causing inconsistencies.
✅ Action Steps:

In Power Platform Admin Center, navigate to Environments > Select your environment > Click Reset Caches.
Restart your browser or clear the cache manually (Ctrl + Shift + R in Chrome).

4. Publish in Small Batches

Since single-entity publishing works, the issue could be a specific entity or component.
✅ Action Steps:

Instead of "Publish All Customizations," try publishing in smaller batches.
Open the solution, select only a few components (e.g., forms, views, fields), and publish them incrementally.
Identify if a specific component is causing the failure.

5. Investigate Solution Import Issues

Even if the solution imports successfully, certain components may not apply due to hidden dependencies.
✅ Action Steps:

Open Power Platform Admin Center → Go to Solutions → Check the import log for warnings.
Look for Solution History Logs (Advanced Settings > Solution History).
If some components are skipped, extract the solution .zip, check the customizations.xml file, and look for missing elements.

6. Use the Classic UI for Publishing (Old Experience)

The modern Maker Portal (Power Apps UI) may sometimes fail to handle large metadata updates.
✅ Action Steps:

Navigate to Classic Solutions Explorer:
- Settings → Customizations → Customize the System → Publish All Customizations.
If the classic UI works, then the issue may be a temporary Power Platform issue.

7. Export & Reimport as a Fresh Unmanaged Solution

If metadata corruption is suspected, try exporting and reimporting the solution.
✅ Action Steps:

Export your solution as Unmanaged.
Delete the solution from Dataverse (Ensure no critical dependencies exist).
Reimport the solution and publish again.

Quick Links

Subscribe to this forum!

Stay up to date on forum activity by subscribing.

Leaderboard > Customer experience | Sales, Customer Insights, CRM

ManoVerse 182 Super User 2026 Season 1

Community site session details