Skip to content

Commit b9757f6

Browse files
authored
Merge pull request sundium#1 from microsoft/master
Pull from source
2 parents 1ce6516 + 7ba20e6 commit b9757f6

40 files changed

Lines changed: 482 additions & 525 deletions

CustomAnalytics/DataFlowVersion/PVA_Analytics_Export_Transform.json

Lines changed: 1 addition & 0 deletions
Large diffs are not rendered by default.
1.45 MB
Binary file not shown.
Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
# Custom analytics solution for Power Virtual Agents - DataFlows version for higher scale bots
2+
3+
If your Bot has significant numbers of monthly sessions, using this version of the report provides improved scalibility. This version does require additional setup, and a Power BI Premium license <https://powerbi.microsoft.com/en-us/pricing/>. The report uses Power BI DataFlows to connect to DataVerse and pre-process some of the compute-intensive transformations of the data.
4+
5+
## Solution components
6+
7+
- Microsoft Dataverse
8+
- Microsoft Power BI DataFlows
9+
- Microsoft Power BI Desktop
10+
- Chat Transcripts control for Power BI - available at <https://github.com/iMicknl/powerbi-botframework-chat-transcripts>
11+
- (Optional) Azure Data Lake Storage v2
12+
13+
## Solution files
14+
15+
- PVA_Analytics_Export_Transform.json - this is the template for a PowerBI DataFlow
16+
- PVA_Dashboard.pbit - Power BI template file
17+
18+
## Installation
19+
20+
### Installation requirements
21+
22+
- One or more Power Virtual Agents bots
23+
- A Power BI account
24+
- [Power BI Desktop](https://powerbi.microsoft.com/en-us/downloads/)
25+
26+
### Installation steps
27+
28+
1. **Edit the DataFlow template**
29+
1. [Find your Dataverse environment URL](https://docs.microsoft.com/en-us/powerapps/maker/data-platform/data-platform-powerbi-connector#find-your-dataverse-environment-url), the URL will be in the format: https://yourenvironmentid.crm.dynamics.com/. You will just need the 'yourenvironmentid' part of the URL
30+
2. Download the file [PVA Analytics_Export_Transform.json](PVA_Analytics_Export_Transform.json?plain=1) and open it in a text editor, e.g. Visual Studio Code.
31+
3. Perform a find and replace on the file - swapping the placeholder `yourdataverse` with your Dataverse environment URL.
32+
33+
2. **Create the DataFlow from the template**
34+
1. Log in to Power BI at <http://powerbi.com>
35+
2. Select the Workspace you wish to deploy the DataFlow to or create a new workspace. Please note that you cannot use 'My Workspace' for this purpose.
36+
3. Select New > DataFlow
37+
4. Select Import Model
38+
5. Select the edited file 'PVA Analytics_Export_Transform.json'. Your DataFlow job should now be ready - test refreshing the data.
39+
6. You should be prompted for credentials, if not go to Settings -> Data source credentials and select organizational account. You can now login with an Azure Active Directory account that has access to the Dataverse environment.
40+
7. Whilst in Settings for your DataFlow, be sure to select 'Enhanced compute engine settings' and select 'On'.
41+
8. If you want to refresh the content periodically, go to Settings -> Scheduled refresh and select the preferred period.
42+
43+
3. **Create your Power BI report**
44+
1. Download the file [PVA_Dashboard_DataFlow.pbit](PVA_Dashboard_DataFlow.pbit?plain=1)
45+
2. Enter the parameters you are prompted for. These are:
46+
1. The name of the Power BI workspace
47+
2. The name of the DataFlow you created
48+
3. The report should pull in the data and render it
49+
4. You can now [publish the report from Power BI Desktop](https://docs.microsoft.com/en-us/power-bi/create-reports/desktop-upload-desktop-files) so that other users can access it.
50+
51+
## Connecting Azure Data Lake Storage for data archival
52+
53+
Please follow the instructions in the main [readme](../readme.md) for details of setting this up. Instead of consuming the DataFlow containing the ConversationTranscript records (stored in Azure Data Lake) in the Power BI report, it should be consumed in the PVA Analytics_Export_Transform DataFlow (change the source of ConversationTranscript from Dataverse to point the Azure Data Lake DataFlow).
54+
55+
## Troubleshooting
56+
57+
There are a few places where the pipeline may break - troublshooting can normally isolate the problem using these steps:
58+
59+
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.
60+
2. Ensure that your Power BI report is connecting to DataFlows. If an error happens when you first pull in data, select 'Transform data' in the navigation menu to open Power Query
61+
1. Refresh each table in the 'Raw Data' folder - these correspond to the data in the DataFlow.
62+
2. If this fails also, test you have permissions to the DataFlow. An easy way to do this is to open the 'bot' query at the top of the query list, and select 'Source' at the top of the 'Applied steps' control. This lists all the DataFlows you have access to.
63+
3. If both of the steps above succeed, but you still have errors, please raise an issue in this repo.

0 commit comments

Comments
 (0)