ManagedEngine ServiceDesk Plus (Zoho) Connector for Power BI
In this article you will learn how to integrate Using ManagedEngine ServiceDesk Plus (Zoho) Connector you will be able to connect, read, and write data from within Power BI. Follow the steps below to see how we would accomplish that. The driver mentioned above is part of ODBC PowerPack which is a collection of high-performance Drivers for various API data source (i.e. REST API, JSON, XML, CSV, Amazon S3 and many more). Using familiar SQL query language you can make live connections and read/write data from API sources or JSON / XML / CSV Files inside SQL Server (T-SQL) or your favorite Reporting (i.e. Power BI, Tableau, Qlik, SSRS, MicroStrategy, Excel, MS Access), ETL Tools (i.e. Informatica, Talend, Pentaho, SSIS). You can also call our drivers from programming languages such as JAVA, C#, Python, PowerShell etc. If you are new to ODBC and ZappySys ODBC PowerPack then check the following links to get started. |
Connect to ManagedEngine ServiceDesk Plus (Zoho) in other apps
|
Video Tutorial - Integrate ManagedEngine ServiceDesk Plus (Zoho) data in Power BI
This video covers following and more so watch carefully. After watching this video follow the steps described in this article.
- How to download / install required driver for
ManagedEngine ServiceDesk Plus (Zoho) integration in Power BI - How to configure connection for
ManagedEngine ServiceDesk Plus (Zoho) - Features about
API Driver (Authentication / Query Language / Examples / Driver UI) - Using
ManagedEngine ServiceDesk Plus (Zoho) Connection in Power BI
Create ODBC Data Source (DSN) based on ZappySys API Driver
Step-by-step instructions
To get data from ManagedEngine ServiceDesk Plus (Zoho) using Power BI we first need to create a DSN (Data Source) which will access data from ManagedEngine ServiceDesk Plus (Zoho). We will later be able to read data using Power BI. Perform these steps:
-
Install ZappySys ODBC PowerPack.
-
Open ODBC Data Sources (x64):
-
Create a User Data Source (User DSN) based on ZappySys API Driver
ZappySys API DriverYou should create a System DSN (instead of a User DSN) if the client application is launched under a Windows System Account, e.g. as a Windows Service. If the client application is 32-bit (x86) running with a System DSN, use ODBC Data Sources (32-bit) instead of the 64-bit version. -
When the Configuration window appears give your data source a name if you haven't done that already, then select "ManagedEngine ServiceDesk Plus (Zoho)" from the list of Popular Connectors. If "ManagedEngine ServiceDesk Plus (Zoho)" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:
ManagedEngineServiceDeskPlus(Zoho)DSNManagedEngine ServiceDesk Plus (Zoho) -
Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.
OAuth Connection for ManageEngine ServiceDesk Plus API [API Help..]
Steps to get ManagedEngine ServiceDesk Plus (Zoho) Credentials : OAuth [OAuth]
To register custom App, perform the following steps (Detailed steps found in the help link at the end)- Go to Zoho API Console
- Click Add Client link
- Select Server-based Applications option
- Enter desired client name (Display purpose only)
- Enter some URL for Company homepage
- For Authorized Redirect URI enter https://zappysys.com/oauth (Or enter your own but we recommend using ZappySys one if possible). This URL must match on Zoho Connector UI.
- Click CREATE.
- Copy Client ID and Secret and paste on Zoho Connector UI.
Fill in all required parameters and set optional parameters if needed:
ManagedEngineServiceDeskPlus(Zoho)DSNManagedEngine ServiceDesk Plus (Zoho)OAuth [OAuth]https://sdpondemand.manageengine.com/api/v3Required Parameters Optional Parameters ClientId Fill in the parameter... ClientSecret Fill in the parameter... Permissions Fill in the parameter... AccountUrl Fill in the parameter... RedirectUrl Fill in the parameter... RetryMode Fill in the parameter... RetryStatusCodeList Fill in the parameter... RetryCountMax Fill in the parameter... RetryMultiplyWaitTime Fill in the parameter... -
Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
-
Click OK to finish creating the data source.
Video instructions
Read ManagedEngine ServiceDesk Plus (Zoho) data in Power BI using ODBC
-
Once you open Power BI Desktop click Get Data to get data from ODBC:
-
A window opens, and then search for "odbc" to get data from ODBC data source:
-
Another window opens and asks to select a Data Source we already created. Choose ManagedEngineServiceDeskPlus(Zoho)DSN and continue:
ManagedEngineServiceDeskPlus(Zoho)DSN -
Most likely, you will be asked to authenticate to a newly created DSN. Just select Windows authentication option together with Use my current credentials option:
ManagedEngineServiceDeskPlus(Zoho)DSN -
Finally, you will be asked to select a table or view to get data from. Select one and load the data!
-
Finally, finally, use extracted data from ManagedEngine ServiceDesk Plus (Zoho) in a Power BI report:
Import ManagedEngine ServiceDesk Plus (Zoho) data into Power BI from SQL Query
If you wish to import ManagedEngine ServiceDesk Plus (Zoho) data from SQL query rather than selecting table name then you can use advanced options during import steps (as below). After selecting DSN you can click on advanced options to see SQL Query editor.
If you type invalid SQL, Power BI may revert to table mode rather than import from Query. Make sure you do not use "$"
it as a table name in SELECT...FROM $
. You can use "_root_"
instead (e.g., SELECT .. FROM _root_). Consider using Custom Object to wrap custom SQL in a Virtual Table. This way, you can see a virtual table in Table mode where you can import multiple objects using the same connection rather than creating a new connection for each custom SQL.
Edit Query / Using Parameters in Power BI (Dynamic Query)
let
vKey=paraAPIKey,
Source = Odbc.Query(
"dsn=ZS-OData Customers",
"SELECT * FROM value WITH (SRC='http://httpbin.org/post',"
& "METHOD='POST',"
& "HEADER='Content-Type:application/json',"
& "BODY=@'{""CallerId"":1111, ""ApiKey"":""" & vKey & """}')")
in
Source
Edit Query Settings after Import
There will be a time you need to change initial Query after dataset import in Power BI. Not to worry, just follow these steps to edit your SQL.
Using DirectQuery Option rather than Import
So far we have seen how to Import ManagedEngine ServiceDesk Plus (Zoho) data into Power BI but what if you have too much data and you dont want to import but link it. Power BI Offers very useful feature for this scenario. Its called DirectQuery Option. In this section we will explore how to use DirectQuery along with ZappySys Drivers. Out of the box ZappySys Drivers wont work in ODBC Connection Mode so you have to use SQL Server Connection rather than ODBC if you wish to use Live data using DirectQuery option. See below step by step instructions to enable DirectQuery mode in Power BI for ManagedEngine ServiceDesk Plus (Zoho) data. Basically we will use ZappySys Data Gateway its part of ODBC PowerPack. We will then use Linked Server in SQL Server to Link API Service and then we will issue OPENROWSET queries from Power BI to SQL Server and it will then call ManagedEngine ServiceDesk Plus (Zoho) via ZappySys Data Gateway.Step-By-Step - How to query ManagedEngine ServiceDesk Plus (Zoho) API in SQL Server
- First read this article carefully, How to query ManagedEngine ServiceDesk Plus (Zoho) API in SQL Server.
- Once linked server is configured we are ready to issue API query in Power BI.
- Click Get Data in Power BI, select SQL Server Database
- Enter your server name and any database name
- Select Mode as DirectQuery
-
Click on Advanced and enter query like below (we are assuming you have created ManagedEngine ServiceDesk Plus (Zoho) Data Source in Data Gateway and defined linked server (Change name below).
Select * from OPENQUERY([MANAGEDENGINE SERVICEDESK PLUS (ZOHO)_LINKED_SERVER],'SELECT * FROM Customers')
- Click OK and Load data ... That's it. Now your ManagedEngine ServiceDesk Plus (Zoho) API data is linked rather than imported.
Working with Gateways in Power BI (Schedule Import)
If the data needs to be updated, it is necessary to create a gateway on-premises. In this new section, we will install a Power BI Gateway and in the next section schedule it to update the ManagedEngine ServiceDesk Plus (Zoho) information.- In the last section, we Published the report. Power BI may ask you to SIGN IN.
- Select the Workspace and select Datasets
- Right-click the report and select Settings.
- The system will ask for a Gateway. Stay here.
-
Use the following link to install a Data Gateway:
https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem
- Run the installer and press Next
- Select the option On-premises data gateway (recommended). This option allows access to multiple users and can be used by more applications than Power BI.
- The installer will show a warning message.
- Select the path to install and check the I accept the terms.
- Specify the email address to use the gateway.
- After entering the email, write the gateway name and a recovery key. Make sure to confirm the recovery key.
Manage gateways and configure the schedule
Once that the gateway is installed we will configure it and add the connection strings.- The next step is to go to manage gateway
- In order to get the connection string, we will need the connection string of the ZappySys API Driver. In the first section of this post, we explained how to configure it. Press Copy Connection String
- Once that the data is copied, add a New data Source. In Data Source Name, enter the Data Source Name of the ZappySys API Driver in step 13 and in Data Source Type, select ODBC. In connection string copy and paste from the clipboard of the step 13 and press Add.
- Once added the gateway. You can see the schedule refresh to On and Add another time to add the time where you want to refresh the data.
Advanced topics
Create Custom Stored Procedure in ZappySys Driver
You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.
Steps to create Custom Stored Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
-
Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
-
Enter the desired Procedure name and click on OK:
-
Select the created Stored Procedure and write the your desired stored procedure and Save it and it will create the custom stored procedure in the ZappySys Driver:
Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
CREATE PROCEDURE [usp_get_orders] @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>' AS SELECT * FROM Orders where OrderDate >= '<@fromdate>';
-
That's it now go to Preview Tab and Execute your Stored Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
Exec usp_get_orders '1996-01-01';
-
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC usp_get_orders @fromdate=''1996-07-30''')
-
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.
Create Custom Virtual Table in ZappySys Driver
ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.
If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.
Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.
-
Go to Custom Objects Tab and Click on Add button and Select Add Table:
-
Enter the desired Table name and click on OK:
-
And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.
-
Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
SELECT "ShipCountry", "OrderID", "CustomerID", "EmployeeID", "OrderDate", "RequiredDate", "ShippedDate", "ShipVia", "Freight", "ShipName", "ShipAddress", "ShipCity", "ShipRegion", "ShipPostalCode" FROM "Orders" Where "ShipCountry"='USA'
-
That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
SELECT * FROM "vt__usa_orders_only"
-
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')
-
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.
Actions supported by ManagedEngine ServiceDesk Plus (Zoho) Connector
ManagedEngine ServiceDesk Plus (Zoho) Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.Parameter | Description |
---|
Parameter | Description |
---|---|
RequestId |
|
Parameter | Description |
---|---|
RequestId |
|
Parameter | Description |
---|---|
RequestId |
|
TaskId |
|
Parameter | Description |
---|---|
RequestId |
|
TaskId |
|
Parameter | Description |
---|---|
RequestId |
|
TaskId |
|
CommentId |
|
Parameter | Description |
---|---|
RequestId |
|
Parameter | Description |
---|---|
RequestId |
|
NoteId |
|
Parameter | Description |
---|---|
RequestId |
|
Parameter | Description |
---|---|
RequestId |
|
WorklogId |
|
Parameter | Description |
---|---|
RequestId |
|
TaskId |
|
Parameter | Description |
---|---|
RequestId |
|
TaskId |
|
WorklogId |
|
Parameter | Description |
---|---|
RequestId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
ChangeId |
|
Parameter | Description |
---|---|
ChangeId |
|
Parameter | Description |
---|---|
ChangeId |
|
TaskId |
|
Parameter | Description |
---|---|
ChangeId |
|
TaskId |
|
Parameter | Description |
---|---|
ChangeId |
|
TaskId |
|
CommentId |
|
Parameter | Description |
---|---|
ChangeId |
|
Parameter | Description |
---|---|
ChangeId |
|
NoteId |
|
Parameter | Description |
---|---|
ChangeId |
|
Parameter | Description |
---|---|
ChangeId |
|
WorklogId |
|
Parameter | Description |
---|---|
ChangeId |
|
TaskId |
|
Parameter | Description |
---|---|
ChangeId |
|
TaskId |
|
WorklogId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
ProblemId |
|
Parameter | Description |
---|---|
ProblemId |
|
Parameter | Description |
---|---|
ProblemId |
|
TaskId |
|
Parameter | Description |
---|---|
ProblemId |
|
TaskId |
|
Parameter | Description |
---|---|
ProblemId |
|
TaskId |
|
CommentId |
|
Parameter | Description |
---|---|
ProblemId |
|
Parameter | Description |
---|---|
ProblemId |
|
NoteId |
|
Parameter | Description |
---|---|
ProblemId |
|
Parameter | Description |
---|---|
ProblemId |
|
WorklogId |
|
Parameter | Description |
---|---|
ProblemId |
|
TaskId |
|
Parameter | Description |
---|---|
ProblemId |
|
TaskId |
|
WorklogId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
ProjectId |
|
Parameter | Description |
---|---|
ProjectId |
|
Parameter | Description |
---|---|
ProjectId |
|
Parameter | Description |
---|---|
ProjectId |
|
Parameter | Description |
---|---|
ProjectId |
|
MilestoneId |
|
Parameter | Description |
---|---|
ProjectId |
|
TaskId |
|
Parameter | Description |
---|---|
ProjectId |
|
TaskId |
|
Parameter | Description |
---|---|
ProjectId |
|
TaskId |
|
CommentId |
|
Parameter | Description |
---|---|
ProjectId |
|
Parameter | Description |
---|---|
ProjectId |
|
NoteId |
|
Parameter | Description |
---|---|
ProjectId |
|
Parameter | Description |
---|---|
ProjectId |
|
WorklogId |
|
Parameter | Description |
---|---|
ProjectId |
|
TaskId |
|
Parameter | Description |
---|---|
ProjectId |
|
TaskId |
|
WorklogId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
ReleaseId |
|
Parameter | Description |
---|---|
ReleaseId |
|
Parameter | Description |
---|---|
ReleaseId |
|
TaskId |
|
Parameter | Description |
---|---|
ReleaseId |
|
TaskId |
|
Parameter | Description |
---|---|
ReleaseId |
|
TaskId |
|
CommentId |
|
Parameter | Description |
---|---|
ReleaseId |
|
Parameter | Description |
---|---|
ReleaseId |
|
NoteId |
|
Parameter | Description |
---|---|
ReleaseId |
|
Parameter | Description |
---|---|
ReleaseId |
|
WorklogId |
|
Parameter | Description |
---|---|
ReleaseId |
|
TaskId |
|
Parameter | Description |
---|---|
ReleaseId |
|
TaskId |
|
WorklogId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
AssetId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
TaskId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
ContractId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
PurchaseOrderId |
|
Parameter | Description |
---|---|
Url |
|
Body |
|
IsMultiPart |
|
Filter |
|
Headers |
|
ManagedEngine ServiceDesk Plus (Zoho) Connector Examples for Power BI Connection
This page offers a collection of SQL examples designed for seamless integration with the ZappySys API ODBC Driver under ODBC Data Source (36/64) or ZappySys Data Gateway, enhancing your ability to connect and interact with Prebuilt Connectors effectively.
List requests [Read more...]
This example shows how to list requests.
SELECT * FROM Requests
Read request details by ID [Read more...]
This example shows how to read extended information about a single request
SELECT * FROM Requests Where id=111112345
Delete request [Read more...]
This example shows how to delete a request by ID.
DELETE FROM Requests Where id=111112345
List request tasks [Read more...]
This example shows how to read all tasks for a single Request ID
SELECT * FROM get_Request_Tasks WITH (RequestId=111112345)
Read request task details [Read more...]
This example shows how to read request task details by single Request ID and Task ID
SELECT * FROM get_Request_Task_Details (RequestId=111112345, TaskId=222212345)
List request task comments [Read more...]
This example shows how to read all comment for specific task
SELECT * FROM get_Request_Task_Comments (RequestId=111112345, TaskId=222212345)
Read request task comment details [Read more...]
This example shows how to read a single comment details for a specific task
SELECT * FROM get_Request_Task_Comment_Details (RequestId=111112345, TaskId=222212345, CommentId=333312345)
List request notes [Read more...]
This example shows how to read all notes for a single Request ID
SELECT * FROM get_Request_Notes WITH (RequestId=111112345)
Read request note details [Read more...]
This example shows how to read request note details by single Request ID and Note ID
SELECT * FROM get_Request_Note_Details (RequestId=111112345, NoteId=222212345)
List request worklog [Read more...]
This example shows how to read all worklogs for a single Request ID
SELECT * FROM get_Request_Worklogs WITH (RequestId=111112345)
Read request worklog details [Read more...]
This example shows how to read request worklog details by single Request ID and Worklog ID
SELECT * FROM get_Request_Worklog_Details (RequestId=111112345, WorklogId=222212345)
List request task worklog [Read more...]
This example shows how to read all worklogs for a single Request Task ID
SELECT * FROM get_Request_Task_Worklogs WITH (RequestId=111112345, TaskId=22222345)
Read request task worklog details [Read more...]
This example shows how to read request task worklog details by single Request Task ID and Worklog ID
SELECT * FROM get_Request_Task_Worklog_Details (RequestId=111112345, TaskId=22222345, WorklogId=333312345)
List projects [Read more...]
This example shows how to list projects.
SELECT * FROM Projects
Read project details by ID [Read more...]
This example shows how to read extended information about a single project
SELECT * FROM Projects Where id=111112345
List assets [Read more...]
This example shows how to list assets.
SELECT * FROM Assets
Read asset by ID [Read more...]
This example shows how to read extended information about an asset
SELECT * FROM Assets Where id=111112345
List purchase orders [Read more...]
This example shows how to list purchase orders.
SELECT * FROM PurchaseOrders
Read purchase order details by ID [Read more...]
This example shows how to read extended information about a single purchase order
SELECT * FROM PurchaseOrders Where id=111112345
List changes [Read more...]
This example shows how to list changes.
SELECT * FROM Changes
Read change details by ID [Read more...]
This example shows how to read extended information about a change
SELECT * FROM Changes Where id=111112345
List contracts [Read more...]
This example shows how to list contracts.
SELECT * FROM Contracts
Read contract details by ID [Read more...]
This example shows how to read extended information about a contract
SELECT * FROM Contracts Where id=111112345
List tasks [Read more...]
This example shows how to list tasks.
SELECT * FROM Tasks
Read task details by ID [Read more...]
This example shows how to read extended information about a task
SELECT * FROM Tasks Where id=111112345
Conclusion
In this article we discussed how to connect to ManagedEngine ServiceDesk Plus (Zoho) in Power BI and integrate data without any coding. Click here to Download ManagedEngine ServiceDesk Plus (Zoho) Connector for Power BI and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).
Download ManagedEngine ServiceDesk Plus (Zoho) Connector for Power BI
Documentation
More integrations
Other application integration scenarios for ManagedEngine ServiceDesk Plus (Zoho)
Other connectors for Power BI
Download ManagedEngine ServiceDesk Plus (Zoho) Connector for Power BI
Documentation
How to connect ManagedEngine ServiceDesk Plus (Zoho) in Power BI?
How to get ManagedEngine ServiceDesk Plus (Zoho) data in Power BI?
How to read ManagedEngine ServiceDesk Plus (Zoho) data in Power BI?
How to load ManagedEngine ServiceDesk Plus (Zoho) data in Power BI?
How to import ManagedEngine ServiceDesk Plus (Zoho) data in Power BI?
How to pull ManagedEngine ServiceDesk Plus (Zoho) data in Power BI?
How to push data to ManagedEngine ServiceDesk Plus (Zoho) in Power BI?
How to write data to ManagedEngine ServiceDesk Plus (Zoho) in Power BI?
How to POST data to ManagedEngine ServiceDesk Plus (Zoho) in Power BI?
Call ManagedEngine ServiceDesk Plus (Zoho) API in Power BI
Consume ManagedEngine ServiceDesk Plus (Zoho) API in Power BI
ManagedEngine ServiceDesk Plus (Zoho) Power BI Automate
ManagedEngine ServiceDesk Plus (Zoho) Power BI Integration
Integration ManagedEngine ServiceDesk Plus (Zoho) in Power BI
Consume real-time ManagedEngine ServiceDesk Plus (Zoho) data in Power BI
Consume real-time ManagedEngine ServiceDesk Plus (Zoho) API data in Power BI
ManagedEngine ServiceDesk Plus (Zoho) ODBC Driver | ODBC Driver for ManagedEngine ServiceDesk Plus (Zoho) | ODBC ManagedEngine ServiceDesk Plus (Zoho) Driver | SSIS ManagedEngine ServiceDesk Plus (Zoho) Source | SSIS ManagedEngine ServiceDesk Plus (Zoho) Destination
Connect ManagedEngine ServiceDesk Plus (Zoho) in Power BI
Load ManagedEngine ServiceDesk Plus (Zoho) in Power BI
Load ManagedEngine ServiceDesk Plus (Zoho) data in Power BI
Read ManagedEngine ServiceDesk Plus (Zoho) data in Power BI
ManagedEngine ServiceDesk Plus (Zoho) API Call in Power BI