@vincenzosgueradev/pptb-connection-reference-governance 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +27 -2
- package/dist/assets/index.js +2 -2
- package/package.json +7 -3
package/README.md
CHANGED
|
@@ -1,6 +1,13 @@
|
|
|
1
1
|
# Connection Reference Governance
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
A solution-first workbench for connection references in one environment. Open a solution, see which references and connections each flow really uses, re-point flows to the reference you choose with the exact change shown as a line diff, and find out what depends on a reference or a connection anywhere in the environment before you remove or delete it. Works on unmanaged solutions in the connected environment.
|
|
4
|
+
|
|
5
|
+
## What sets it apart
|
|
6
|
+
|
|
7
|
+
- **It starts from the flow.** One row per flow with the reference, connector and connection behind every action, and the same data grouped by reference. You choose which flow points where, not only which duplicates merge.
|
|
8
|
+
- **It shows the change before it is written.** The preview is the exact definition that will be stored, as a line diff, with what each row is now and will be, and a per-row result and read-back afterwards.
|
|
9
|
+
- **It looks beyond the solution.** Dependencies are read for the whole environment (flows, Copilot Studio agents, apps, other components, in any solution) and the Connections area covers the connections themselves, with what depends on each one.
|
|
10
|
+
- **It says what it could not see.** A connection nothing was found for says "No dependency found", never "unused", and each source reports how much it read.
|
|
4
11
|
|
|
5
12
|
## Features
|
|
6
13
|
|
|
@@ -23,6 +30,19 @@ See which connection references every flow in a solution uses, find references w
|
|
|
23
30
|
- Flows that are turned on cannot be changed in Dataverse. With your permission (off by default, a block in the studio with a warning, the list of flows and a second acknowledgement) the tool turns them off for the change and on again afterwards, even when the write fails; a flow left off is named in the result and in the report.
|
|
24
31
|
- Managed solutions cannot be changed, so they are not offered: a disabled Managed tab shows how many there are.
|
|
25
32
|
|
|
33
|
+
## Overlap with EnvVar & ConnRef Matrix
|
|
34
|
+
|
|
35
|
+
The listed tool **EnvVar & ConnRef Matrix** also works with connection references: it binds them to connections, consolidates duplicate references by re-pointing flows, deletes unused references after a dependency check and flags flows that point at a missing reference. Its centre is the **comparison of environments** and the deployment of values between them (a matrix of environment variables and references across environments, copying values, `deploymentSettings.json`). This tool stays in **one environment** and starts from the solution and its flows. What it adds:
|
|
36
|
+
|
|
37
|
+
- The **per-solution flow-to-reference view**: one row per flow with every reference, connector and connection it uses, and the same data grouped by reference.
|
|
38
|
+
- **Re-point any flow** to another reference of the same connector, chosen flow by flow, with a line diff of the flow definition before anything is written (not only the merge of duplicates).
|
|
39
|
+
- **Create a connection reference** in the open solution, with checked names and an optional connection.
|
|
40
|
+
- **Remove references from a solution** while they stay in the environment (as well as delete them).
|
|
41
|
+
- **Dependencies in the whole environment** for a reference or a connection, in any solution: flows, Copilot Studio agents, apps and other components, with what lies outside the solution.
|
|
42
|
+
- The **Connections** area: the connections of the environment with status, what depends on each one, and a guarded delete.
|
|
43
|
+
|
|
44
|
+
If you compare environments or bind references from a settings file, use that tool; the two do not need each other.
|
|
45
|
+
|
|
26
46
|
## Screenshots
|
|
27
47
|
|
|
28
48
|
All screenshots are real, taken on a test environment with sample data.
|
|
@@ -158,10 +178,15 @@ AI helped write a substantial part of the code and tests. The author reviews and
|
|
|
158
178
|
|
|
159
179
|
## Updates
|
|
160
180
|
|
|
161
|
-
Page text reviewed for version 0.1.
|
|
181
|
+
Page text reviewed for version 0.1.1.
|
|
162
182
|
|
|
163
183
|
Full history: https://github.com/vincenzosgueradev/connection-reference-governance/blob/main/CHANGELOG.md
|
|
164
184
|
|
|
185
|
+
### 0.1.1 - 2026-11-14
|
|
186
|
+
|
|
187
|
+
- The tool now follows the Power Platform ToolBox theme (light or dark) instead of the operating system theme, and changes with it while open.
|
|
188
|
+
- Added a section that explains how this tool relates to EnvVar & ConnRef Matrix and what it adds, and a short summary of what sets this tool apart.
|
|
189
|
+
|
|
165
190
|
### 0.1.0 - 2026-11-13
|
|
166
191
|
|
|
167
192
|
- Added a view of every flow of an unmanaged solution with the connection references it uses, and a view grouped by connection reference.
|