Skip to content

v1.1.0 - Dataverse Integration: Auto Topic Resolution, Orchestrator Identification & Enhanced Trace Types

Latest

Choose a tag to compare

@rquattros rquattros released this 19 Apr 19:06

What'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 of 3399ac22…
  • 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 β€” VariableAssignment traces show scope (Topic/Global), variable name, and formatted value
  • Topic Redirect β€” DialogRedirect traces 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

  1. A Microsoft Entra ID App Registration (SPA)
  2. Dynamics CRM user_impersonation API permission
  3. 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)

  1. Go to Azure Portal β†’ App registrations β†’ + New registration
  2. Name: Copilot Studio Trace Viewer
  3. Platform: Single-page application (SPA) with redirect URI pointing to where you host index.html (e.g. https://yourusername.github.io/CopilotStudioTraceViewer/)
  4. Go to API permissions β†’ + Add a permission β†’ Dynamics CRM β†’ user_impersonation
  5. Copy the Application (Client) ID and Directory (Tenant) ID
  6. Assign the Bot Transcript Viewer security role in Power Platform Admin Center
  7. (Recommended) Add Read on the Bot Component table to your security role for auto topic resolution
  8. 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 main branch
  • Localhost: npx http-server -p 8080 (add http://localhost:8080 as redirect URI)

Full Changelog

  • Auto-fetch botcomponents from Dataverse with per-bot caching
  • friendlyComponentId() for GUID β†’ display name resolution
  • Orchestrator purple border + filter button (both viewers)
  • VariableAssignment trace rendering with scope + formatted value
  • DialogRedirect β†’ Topic Redirect with cyan badge and resolved names
  • 15 DialogTracingInfo action-type badges with color coding
  • README: documented all 3 Dataverse tables, security role setup, troubleshooting
  • README: removed duplicate content sections