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

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

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

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

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

This release contains the following changes

Flows

• The generated graphs for Flows now try to follow the colour scheme from the Power Automate studio. This is an early version, and not all colours are correct yet. But it is a beginning, improvements to take place regularly from now onwards!
• The graph for Flows that had multiple parallel actions after a trigger was not correct, only one node was connected to the trigger (as reported in #102). This has been fixed. Additionally, merging parallel actions also weren't rendered correctly, this has been fixed as well

Solutions

• There was an issue with Dataverse tables not getting processed correctly (see #97). This has been fixed

Canvas Apps

• smaller fix that helps with app parsing (code in comments is no longer parsed, as it should be) modery/PowerDocu.Common@6e0a038

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

Only 2 smaller bugfixes are included in this release

Flows

• Fixing issue #93, where trigger conditions were not properly documented

Solutions

• In rare cases documenting Dataverse tables ran into an exception. This has been fixed

Canvas Apps

• no updates

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

Added 2 new features as part of this release!

Flows

• The sort order of Flow actions in the documentation is now configurable. You can choose to have them sorted by name (which is the default), or you can have them sorted by their order of appearance - that is, roughly from top to bottom (similar to how they appear in the designer).
• bug fix: Flow action descriptions were not always properly rendered if they contained invalid characters. This has been fixed

Solutions

• Dataverse tables are now documented with their columns! This first release provides the table's name and description, and some details for the columns in the table

Canvas Apps

• no updates

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

This is mostly a bugfix release and contains the following stability improvements:

Canvas Apps

• no updates

Flows

• some Flows were not properly documented. Actions that were using arrays sometimes failed to be documented, sometimes the values were not documented properly. This should be fixed now. (#68)
• Notes on Actions are now rendered in the diagrams. Planning to make this a configurable option in the future

Solutions

• stabilised parsing of privileges
• stabilised parsing of solution details (mentioned in #53)
• started to prepare documenting Dataverse tables. No real big change here yet, likely in the next version

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

This is a smaller release (and only while doing a final review before pressing publish did I realise that a v.1.1.1 might have been better) which only contains some smaller things

Canvas Apps

• no longer documenting the "TableDefinition" property for datasources, as it can become too large. Will possibly document it separately in the future, but skipping it for the moment
• datasources are now documented in separate Markdown files

Flows

• documenting the Foreach property of "Apply to each" actions, showing on which items the action runs

Solutions

• adding more detail to Security Roles. Table names are still showing the internal name only, to be enhanced in a future release
  

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