How tihanajk/apireferencefinder works
Project type and purpose
• This is a single‐project XrmToolBox plugin (desktop‐based .NET tool) whose purpose is to scan Dynamics 365/Power Platform environments for API references in Power Automate flows and web resources.
File structure
• Top‐level files
• APIReferenceFinder.csproj, .sln, .nuspec – defines the plugin project, dependencies, packaging
• APIReferenceFinderPlugin.cs – implements the IPlugin interface/entry point
• APIReferenceFinderPluginControl.* – WinForms or WPF control for UI
• Settings.cs, app.config – plugin configuration
• MyToolDesign.excalidraw – draft of UI or flowchart
• No separate frontend/backend folders because it all lives in one .NET assembly loaded by XrmToolBox at runtime.
README
• Confirms it’s an XrmToolBox tool to find API calls in flows and web resources.
Main components
a. XrmToolBox Host
• Acts as a container that loads this plugin DLL via the XrmToolBox plugin SDK.
b. Plugin Assembly (APIReferenceFinder.dll)
• Entry point (IPlugin implementation in APIReferenceFinderPlugin.cs)
• UI layer (APIReferenceFinderPluginControl)
• Business/Scan logic (methods that query and parse flows and web resources)
• Configuration (Settings.cs, app.config)
c. Dataverse / Power Platform Environment
• The target organization where flows & web resources live
• Exposed via the Dataverse Web API / SDK assemblies (referenced in the .csproj)
d. External Services/APIs
• Power Automate Web API (to retrieve flow definitions)
• Dataverse Web API (to retrieve web resources)
e. Local Resources
• Any export files or logs you write to disk (if implemented)
Relationships & Data Flow
1. User launches XrmToolBox → selects APIReferenceFinder plugin in the list
2. XrmToolBox loads the plugin DLL → invokes Initialize() on APIReferenceFinderPlugin
3. PluginControl UI renders (buttons, grids, etc.)
4. User clicks “Scan” → UI calls business logic methods
5. Business logic uses the Dataverse connector from XrmToolBox SDK to authenticate & call
– Dataverse Web API → retrieve web resources
– Power Automate Web API → retrieve flow definitions
6. Plugin parses JSON/XML payloads → discovers API references
7. Plugin returns results to UI → displays in a grid or tree view
8. (Optional) Plugin writes export files or logs locally
Architectural patterns & design principles
• Plugin pattern: loaded by host via a well‐defined IPlugin interface
• Separation of Concerns:
• Plugin entry point vs. UI control vs. scanning logic vs. configuration
• Use of the XrmToolBox SDK as an abstraction over raw HTTP calls