Repository navigation
v1.1.0 - Dataverse Integration: Auto Topic Resolution, Orchestrator Identification & Enhanced Trace Types
LatestWhat's New
π Auto Topic Name Resolution from Dataverse
When loading a conversation transcript from Dataverse, the viewer now automatically fetches bot components from the botcomponents table and resolves raw component GUIDs to friendly display names β no manual upload needed.
- Topic Redirects (
DialogRedirect) now display as β Greeting instead of3399ac22β¦ - Component names appear in both the timeline title and the expanded detail panel
- Results are cached per bot β switching between conversations from the same bot doesn't re-fetch
π£ Orchestrator Step Identification
Orchestrator events (DynamicPlanReceived, DynamicPlanStepTriggered, DynamicPlanStepBindUpdate, DynamicPlanStepFinished, DynamicPlanCancelled) are now visually distinct:
- Purple left border on the step card
- Dedicated Orchestrator filter button to show/hide orchestrator-only steps
π New Trace Type Badges
- Var Assignment β
VariableAssignmenttraces show scope (Topic/Global), variable name, and formatted value - Topic Redirect β
DialogRedirecttraces with cyan badge, resolved topic name, and full component ID - Dialog Tracing action-type badges β 15 distinct action types (SetVariable, SendActivity, Question, InvokeFlowAction, BeginDialog, ConditionGroup, etc.) each with their own color-coded badge
Dataverse Setup β How to Use
Prerequisites
- A Microsoft Entra ID App Registration (SPA)
- Dynamics CRM
user_impersonationAPI permission - Read access to these Dataverse tables:
| Table | Entity Name | Purpose |
|---|---|---|
| Bot | bots |
Populate agent filter dropdown |
| Conversation Transcript | conversationtranscripts |
List and load transcripts |
| Bot Component | botcomponents |
Resolve GUIDs to friendly topic names |
Quick Setup (5 minutes)
- Go to Azure Portal β App registrations β + New registration
- Name:
Copilot Studio Trace Viewer - Platform: Single-page application (SPA) with redirect URI pointing to where you host
index.html(e.g.https://yourusername.github.io/CopilotStudioTraceViewer/) - Go to API permissions β + Add a permission β Dynamics CRM β
user_impersonation - Copy the Application (Client) ID and Directory (Tenant) ID
- Assign the Bot Transcript Viewer security role in Power Platform Admin Center
- (Recommended) Add Read on the Bot Component table to your security role for auto topic resolution
- Open the viewer, enter your Environment URL + Client ID + Tenant ID, and click Connect
See the full step-by-step guide in the README for detailed instructions with screenshots.
Hosting Options
- GitHub Pages (recommended): Fork the repo β Settings β Pages β Deploy from
mainbranch - Localhost:
npx http-server -p 8080(addhttp://localhost:8080as redirect URI)
Full Changelog
- Auto-fetch
botcomponentsfrom Dataverse with per-bot caching friendlyComponentId()for GUID β display name resolution- Orchestrator purple border + filter button (both viewers)
VariableAssignmenttrace rendering with scope + formatted valueDialogRedirectβTopic Redirectwith cyan badge and resolved names- 15
DialogTracingInfoaction-type badges with color coding - README: documented all 3 Dataverse tables, security role setup, troubleshooting
- README: removed duplicate content sections