Skip to content

Commit 2ca6ca3

Browse files
authored
Merge pull request microsoft#35 from MattFarm/master
Bug fixes to CSAT & Total Topic Count calculation.
2 parents b97837e + 36f185a commit 2ca6ca3

3 files changed

Lines changed: 16 additions & 6 deletions

File tree

CustomAnalytics/PVA_Dashboard.pbit

2.29 KB
Binary file not shown.
122 KB
Loading

CustomAnalytics/readme.md

Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,30 @@
11
# Custom analytics solution for Power Virtual Agents
2+
23
This solution allows customers to create a Power BI dashboard for their Power Virtual Agents chatbots
34

5+
<img src="img/PVA_Analytics.png" width="797" alt="Custom Analytics example screenshot">
6+
47
## Solution components
8+
59
- Microsoft Dataverse
610
- Microsoft Power BI DataFlows
711
- Microsoft Power BI Desktop
812
- (Optional) Azure Data Lake Storage v2
913

1014
## Solution files
15+
1116
- PVA_Analytics_Export.json - this is the template for a PowerBI DataFlow
1217
- PVA_Dashboard.pbit - Power BI template file
1318

14-
# Installation
19+
## Installation
20+
21+
### Installation requirements
1522

16-
## Installation requirements
1723
- One or more Power Virtual Agents bots
1824
- A Power BI account
1925

20-
## Installation steps
26+
### Installation steps
27+
2128
1. Edit the DataFlow template
2229
1. FInd the server url associated with your Dataverse environment (it will look like https://yourservice.crm.dynamics.com)
2330
2. Open the file 'PVA Analytics_Export.json' in a text editor
@@ -31,23 +38,26 @@ This solution allows customers to create a Power BI dashboard for their Power Vi
3138
3. Create your PowerBI report
3239
1. Open the file PVA_Dashboard.pbit
3340
2. Enter the parameters you are prompted for. These are:
34-
1. The name of the Powe rBI workspace
41+
1. The name of the PowerBI workspace
3542
2. The name of the DataFlow you created
3643
3. The report should pull through the data and render it
3744
4. You can now save the report to share through the Power BI portal
3845

3946
## TBD Connecting Azure Data Lake Storage for data archival
47+
4048
Using Azure Data Lake Storage v2, DataVerse can archive the data used in this report, to support datasets greater than 30 days. This pattern is in developement.
4149

42-
# Using the report
50+
## Using the report
51+
4352
The report is based on what is shared through the Power Virtual Agents portal, but with some important differences:
4453

4554
- The report includes all bots in your environment
4655
- The report includes a date filter - and can support a range of dates greater than the 30 days supported natively in Dataverse
4756
- The report includes all trace data emitted with the bot, allowing users to build reports on data import to them
4857
- The report can be shared with users and business decision makers without access to Power Virtual Agents
4958

50-
# Troubleshooting
59+
## Troubleshooting
60+
5161
There are a few places where the pipeline may break - troublshooting can normally isolate the problem using these steps:
5262

5363
1. Ensure that data is being pulled in to your DataFlow correctly. Open the DataFlow for editing (select 'edit entities'), and on each of the tables, select refresh to ensure that data is being populated.

0 commit comments

Comments
 (0)