Dynamics Community Forum Thread Details

Hello AH-31052106-0,

You're absolutely correct. Unpublished changes in Dynamics 365 (Dataverse) solutions are indeed isolated and not visible to regular end-users interacting with the live application. They are only visible within the solution editing environment.

Unfortunately, there isn't a direct, built-in "admin view" or a simple button to see all unpublished changes across the entire live environment. However, there are ways an administrator can investigate and manage these changes:

1. Inspecting Individual Solutions:

Solution Editor:
- The most direct way is to open each solution in the solution editor.
- Within the solution editor, the administrator can see the components that have been modified but not published.
- This method requires manually checking each solution, which can be time-consuming if you have many solutions.

Filter by Modified Date:
- Within the solution editor, you can often sort or filter components by their "Modified On" date. This helps identify recent changes.

2. Using the Web API (Advanced):

Retrieve Solution Components:
- You can use the Dynamics 365 Web API to retrieve a list of components within a solution.
- You can then filter these components based on their ismanaged property (to exclude managed components) and their modifiedon date.
- This method requires some coding knowledge.

Power Automate:
- You could create a Power Automate flow that uses the Web API to retrieve the solution components and send a notification to administrators.
- This can automate the process of checking for unpublished changes.

3. Auditing (For Specific Changes):

Auditing:
- If auditing is enabled on the entities and fields being modified, the audit logs can provide some information about changes.
- However, auditing doesn't directly indicate whether a change is published or unpublished.
- It mainly shows who made the change and what was changed.

Limitations:
- Auditing is entity-specific, not solution-specific.
- It doesn't provide a comprehensive view of all unpublished changes.

4. Monitoring Changes (Manual, But Proactive):

Change Management Process:
- Implement a strict change management process that requires developers to document their changes before publishing.
- This helps administrators keep track of modifications.

Communication:
- Encourage developers to communicate their changes to administrators.
- This can be done through email, chat, or a dedicated change management tool.

Key Considerations:

Scope of Changes: Determine the scope of changes you need to monitor. Are you concerned about all unpublished changes or only specific types of changes?
Frequency of Checks: How often do you need to check for unpublished changes?
Automation: Consider automating the process of checking for unpublished changes using Power Automate or the Web API.

In summary, there's no single, easy "show all unpublished changes" button. The most common method involves manually checking solutions within the editor. For more automated and comprehensive monitoring, you would have to build a custom solution using the Web API and Power Automate. The most effective method is to have a good change management process in place.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

Community site session details

Unpublished Changes

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Meet the Microsoft Dynamics 365 Contact Center Champions

Congratulations to the March Top 10 Community Leaders

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates