Integrating your BRYTER application with Microsoft Power BI enhances the user experience by providing seamless data visualization through interactive dashboards. Real-time data integration enables swift decision-making by monitoring changes as they happen.
To implement this solution, leverage BRYTER Connect to optimize user experiences and foster better business outcomes.
This tutorial outlines the process of connecting BRYTER and Microsoft Power BI.
Implementation
π‘ To implement this solution, you need a Microsoft Power BI Desktop and a BRYTER Connect license.
-
Open Microsoft PowerBI on your desktop and click on Get Data.
-
Search for Web among the connectors as the data source and select the Web connector. Then, click on Advanced on the next page. Use the following parameters to complete the configuration:
-
URI parts:
https://<tenant>.bryter.io/api/databases/<publisheDdatabaseId>/entries
-
<tenant>
: replace this with your BRYTER tenantβs nameΒ -
<publishedCaseDatabaseId>
: replace this with the published database id that you will find in step 3.
-
-
HTTP request header parameters (optional):
-
Type Authorization into the left column
-
Type
Bearer <API KEY>
into the right column<API KEY>
: Replace this with the databaseAPI key
you will generate in step 3.
-
-
-
To complete step 2, we need to
publishedCaseDatabaseId
. We will make an API call for this:
-
To make an API call, you can use a tool like Insomnia or Postman.
-
Select GET as the request type.
-
Paste the URL as below:
https://<tenant>.bryter.io/api/databases/environments/<environment id>
-
<tenant>
: replace this with your BRYTER tenantβs name -
<environment id>
: replace this with theEnvironment ID
. Learn here how to obtain the Environment ID. Usually, you will want to visualize data from databases in the Live environment, but see below on how to visualize data from multiple environments, e.g., Testand client environments.
-
-
Select Bearer as the authorization type and insert the API key. Check this article to generate an API key.
-
Click on the Send button to make the API call. An example result may look like this:
{ "data": { "databases": [ { "name": "database name", "caseDatabaseId": "YpPgQY2nRuK-S2pa6WBVog", "publishedCaseDatabaseId": "C01qgWZNT4O5Ne3ZbT3FpQ" }, { "name": "other database name", "caseDatabaseId": "N-EDkQzYSgmOzAi2IUoS2Q", "publishedCaseDatabaseId": "QziEwjj5S2SKAJGEDYuySQ" } ] } }
-
Find the database you want to use as a data source in Power BI and insert its
publishedCaseDatabaseId
to the URI parts in step 2.
The response lists all databases for the given environment. So there may be cases where there are a number of databases with the same name. In this case, you need to determine the correct one by using thecaseDatabaseId
, which is shown as part of the URL in the BRYTER Author area when configuring a database.
4. Create the dashboard in Power BI and publish it on the web.
5. Create a BRYTER module to embed your Power BI dashboard in the BRYTER application, as explained here.
β To implement this solution, your BRYTER contact person needs to enable environment variables in built-in values.
-
As described in step 3, obtain the
publishedCaseDatabaseId
and the API key for the second environment for which you want to visualize data. -
Create a new Web connector for this environment using the
publishedCaseDatabaseId
and API key. -
Create a similar dashboard on PowerBI and publish it on the web.
-
Next, adapt the module that displays the dashboard by redirecting to it. We now want this module to decide which dashboard to display, depending on the environment the module is in. Follow the steps below:
-
Insert an Empty action before the Result node.
-
Add another result node following the Empty action.
-
Add conditions to the transitions leading from the empty node to the result nodes. Define the conditions as follows:
-
For the transition leading to the original Live version of the dashboard, set the condition to: Environment Name = Live.
-
For the transition leading to the other version of the dashboard (e.g., Test), set the condition to e.g.: Environment Name = Test.
-
-
Publish the module to the second environment.
-
If you have any questions, please contact our Technical Success Team at support@bryter.io.