v.3.0.1 Release

The 3.0.1 release contains the following updates and optimisations:

General

• First version of Business Process Flow documentation has been added
• Performance improvements: concurrent documentation of Cloud Flows and Canvas Apps (instead of documenting them each sequentially), leading to faster output generation

Copilot Studio Agents

• MCP servers are now documented with available information, listed under tools

Power Apps

• Optimisation: we no longer document the WadlMetadata and NativeCDSDataSourceInfoNameMapping properties of Dataverse data sources, which previously led to hundreds of additional documentation pages
• Fixed #202 , where the resources folder was not properly created for Markdown documentation

Solutions

• Documented web resources, Ribbon Customizations

GUI

• Starting the documentation process no longer blocks the interface
• A progress tracker now shows the documentation status in much more detail

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.3.0.0 Release

3.0.0 is a major release that introduces documentation support for three new component types: Copilot Studio Agents, AI Models/Prompts, and Model-Driven Apps. The parsing and documentation architecture has also been significantly refactored to be more flexible and futureproof. A range of other improvements and fixes are included as well.

General

• Major update to the parsing and documentation process, making it more flexible and futureproof
• Links from component documentation (Apps, Flows, etc.) now link back to the Solution overview
• Conditional links between output documents are now supported for HTML and Markdown output formats
• Control to define if default Dataverse columns (Created, Created By, ....) should be included in documentation
• Dataverse tables now have their views and forms documented. Each form has a SVG/PNG mockup generated
• OOTB Security Role names have been added, so that these are used in the documentation instead of their GUIDs
• Word document enhancements
  • headers are now centralised in styles file
  • Table of Contents can be added to output (manual refresh required)
  • Spellcheck in generated documents has been disabled by default, which also helps to improve performance when opening Word docs
• Updated from .NET 8 to .NET 10, as .NET 8 is nearing end of support in November 2026

Copilot Studio Agents (NEW)

• Agents in solutions are now getting documented!
• Agent topics are documented with graphs
• Agent topic flow is documented
• Agent variables usage is documented

AI Models/Prompts (NEW)

• AI Models and Prompts contained in solutions are now getting documented

Model-Driven Apps (NEW)

• Model-Driven App (MDA) documentation is now supported in a first version

Power Apps

• instead of one general and one detailed Word document being generated, we now generated one overview document and one Word document per screen, resulting in smaller Word files overall
• Changed how the Controls overview is rendered in Word, moving away from tables to indentation. Faster processing and rendering when openening the Word document
• New default values for modern controls were added
• Using PowerFx to extract information about variables instead of the previous more manual approach. Parsing is faster and more reliable now
• Stopped documented "Auxiliary Datasources", specifically Dataverse views and statecodes (tables are still documented)

Flows

• Flow graph design has been updated. Action nodes in diagrams now have rounded edges and coloured borders, further improving the visual alignment with the Power Automate designer
• Flow Type gets documented: Cloud Flow, Agent Flow

Solutions

• Improved relationships between Dataverse Tables in the generated graph
• Workflow overview in solution documentation improved
• Fixed sort order of components in solution documentation
• HTML output now contains collapsible navigation
• Environment Variables are now shown in a clearer way in Solution documentation overview

GUI

• Range of additional controls helping you defined what should be documented

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.2.5.0 Release

2.5.0 introduces HTML as output format and allows you to see a small progress overview when starting the documentation process. A few other fixes/enhancements were also made:

General

• HTML is now a supported output format! A standardised template gets generated, but the style.css can be modified as needed
• When the documentation gets started, there is a progress indicator showing which solution/app/Flow files are currently being processed
• Dataverse OptionSets are now getting documented
• Dataverse tables are now also documenting the record ownership ("User or team" or "Organization")
• Updating the connectors and their icons is now much faster
• Updated System.Drawing.Common and Microsoft.PowerFx.Core packages to latest version

Apps

• The App Info section for Canvas Apps gets documented correctly across output formats (previously only in Word)

Flows

• The folder names for documented Flows now no longer contain the Flow GUID

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.2.4.1 Release

As 2.4.0 introduced a bug that stopped the documentation of Flows, this release is relatively short:

General

• Updated Rubjerg.Graphviz to the latest version (3.0.4). This removes the bug that stopped the documentation of Flows from working
• Added a checkbox under settings that lets you control if you want the app to check for new release on app launch

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.2.4.0 Release

UPDATE: This new version throws an error when you try to document Flows. Apparently I made a mistake during my testing before releasing this version and didn't catch this problem. Issue has been identified, waiting for the maintainer of another package to correct it.

This release contains the following changes

General

• Added a fix for CA2326 (https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2326)
• added a button that brings you to the folder of the solution/zip that has been documented (documentation in subfolders), Button appears after documentation has been created
• Updated Nuget libraries to latest versions

Power Apps

• minor fix to render code correctly in the documentation

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.2.3.0 Release

This release contains the following changes

General

• You can now select what you want to get documented: Solution, Flows, Apps, as well as which app details (app properties, variables, datasources, resources, controls)
• Dataverse table auditing (enabled or disabled) is now getting documented
• Updated Nuget libraries to latest versions
• Updated gLib and gObject DLLs (part of Graphviz) manually, as older versions contained a vulnerability

Power Automate

• documenting solutions that contain Power Automate Desktop Flows threw an error. Desktop Flows are now excluded from documentation (f32cd5f) (fixing #176 #170 )

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.2.2.0 Release

The first release in 2025 contains the following changes

General

• You can now decide if you want to create a "full set of documentation" (that is, Word/Markdown/Both documentation and the corresponding images for Flows and Dataverse relationships) or just the images.
• Environment Variables are now getting documented (#145)
• Folder names do no longer contain the IDs of the apps/Flows (#147)
• Flow information in Solution overview now contains information about the trigger type
• Updated Nuget libraries. Fontawesome.sharp 6.6.0, DocumentFormat.OpenXml 3.2.0, HtmlAgilityPack 1.11.72, System.Drawing.Common 9.0.1

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.2.1.0 Release

The latest release is mainly focused on an improved user interface experience.

This release contains the following changes

General

• The GUI has been updated. Configuration options and detailed log are now on seperate tabs. Documentation process only starts when you click the new "Start documentation" button. (#140)
• It is now possible to save your current configuration and use it as the default whenever PowerDocu launches
• Improved error handling, providing more information when something fails. This will help with future support
• Fix for #160

Power Apps

• You can now configure if you want to get sample data sources documented (#122)

Flows

• Fix for #153

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.2.0.1 Release

It has been a while since the last release. However, this current release is mainly getting published to fix some urgent issues:

This release contains the following changes

General

• All referenced libraries have been updated to their latest versions
• Microsoft removed the API that listed all connectors, which broke the functionality to get the connector icons. Thus, I had to switch to scraping the official connector documentation page for the list of connectors
• Fixing issue #120
• Connector icons get moved to %APPDATA%/PowerDocu folder (issue #128)

Flows

• Flow description gets documented (issue #143)

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.2.0.0 Release

After a longer hiatus, I am excited to announce the next release of PowerDocu. While there are few functionality changes, the move from .NET Core 3.1 to .NET 8 as well as using the latest versions of all referenced libraries mean that this release receives an updated major version number to highlight the significance of these changes.

This release contains the following changes

General

• Updated to use .NET 8
• All referenced libraries have been updated to their latest versions
• Generated graphs (SVG, PNG) now use Helvetica font by default

Flows

• Adding a label to edges that are in a "Switch" and showing switch condition on Switch nodes, making it easier to see more details on the Switch options

Solutions

• Creating a Graph that shows the relationship between Dataverse tables in the solution
• Fix for issue #110

CLI

• it is possible to run PowerDocu.GUI.exe from a command line interface (also, Azure DevOps pipelines)! Thanks to @a1dancole , this functionality can now be tested. Check out #111 (comment) for a few more details - a more detailed guide will come in the upcoming weeks

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions