For many years, our IT Admins have asked us to enable them to build their own call quality/reliability reports. We are happy to share that you are now empowered to build your own reports, powered by Advanced Call Quality Dashboard data.
Microsoft Call Quality Power BI Connector Installation
The process for installing a custom connector and adjusting security to enable use of the connector is described in detail in the Power BI documentation. For the sake of simplicity though, a quick explanation is provided below:
If a new version of the Microsoft Call Quality Power BI Connector is released, simply replace the old connector file in the Custom Connectors directory with the new file.
Microsoft Call Quality Power BI Connector Setup
In order to build a report and run queries, you will first need to connect to the CQD data source. Follow the steps below in order to connect:
If any of the steps during this setup process were not completely clear, a more detailed explanation of the process can be found here.
Building Queries using Microsoft Call Quality Power BI Connector
Once setup is complete, you should see the names of several hundred dimensions and measures load in the Fields pane. Constructing actual queries from here is simple, just select the dimensions and measures you want for your query, then drag and drop them onto the page. Here’s a more detailed explanation, with a simple example:
Important Note: Call Quality Dashboard requires a measure for any query to run. Failure to add a measure to a query will cause that query to fail.
Note: CQD queries require at least one measure in order to run. If your query does not load, double check that you have included a measure in the query.
Creating a Drill-through Report
Drillthrough in Power BI allows you to create focused reports that you can quickly filter using the values of other reports as context. Once you know how to create your first query with the Microsoft Call Quality Power BI Connector, creating a drillthrough is even simpler.
Unlike Advanced CQD, Power BI supports non-sequential drill-through. As long as a query includes the necessary dimension, it can drill-through to any other page.
Despite making use of Power BI, not all Power BI functionality is support by the Microsoft Call Quality Power BI Connector, either as a result of limitations on CQD data model (such as non existent data) or on DirectQuery connectors in general. The list below notes some of the Connector’s more noteworthy limitations, but this list should not be considered exhaustive:
Please note, although the Connector is in preview, these limitations are unlikely to change with the final release of the Connector. Most of these issues are either restrictions to DirectQuery connector design in Power BI or fundamental to the design of the CQD data model.
Because the Microsoft Call Quality Power BI Connector is less restricted than the browser app in terms of kinds of queries you can construct, you may occasionally encounter a number of errors while building your queries. In the event that you receive an error message of the type “CQDError. RunQuery – Query Execution Error”, reference the list below with the ErrorType number provided in order to troubleshoot the possible issue with the query. The following are the most common Error Type codes you may encounter with the CQD Power BI Connector:
If you encounter any additional errors outside of this scope, please notify the CQD team so that we can help troubleshoot the issue and update the documentation as appropriate.
Call Quality connector queries should be designed with drillthrough functionality in mind. Instead of trying to load all the data at once, and then slicing down with filters, start with broader, low-cardinality queries and drill down to high-cardinality queries. For instance, when attempting to diagnose which subnets contribute most to quality issues, it's helpful to first identify those regions and countries which contribute to the problem, then drill down to the subnets in that region or country. The Call Quality connector templates have been designed in this manner in order to act as an example.
Other useful best practice links:
Query performance for the various templates is actually the same in both the browser and in the connector. Just like any other standalone app, Power BI adds its authentication and rendering time to our performance. In addition, the difference comes in the number of concurrent queries being run. Because the in-browser version of CQD had less well-developed and information-dense visualization options, most of our reports were limited to loading 2-3 queries at a time. On the other hand, the connector templates often display 20+ concurrent queries. If you wish to build reports that are just as responsive as the older ones you were used to, try creating reports with no more than 2-3 queries per tab.
1 Certain processes and apps (e.g. OneDrive) may cause your Documents root folder to change; make sure that the Power BI Desktop\Custom Connectors directory is placed inside of the current root folder Documents folder.
2 The login credentials you use for CQD do not need to be the same credentials you use for logging into the Power BI Desktop app itself.
Copyright 2020 Microsoft Corporation
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.