Home » API Integration Hub » Power BI Connectors » DropBox Connector for Power BI

DropBox Connector for Power BI

In this article you will learn how to quickly and efficiently integrate DropBox data in Power BI without coding. We will use high-performance DropBox Connector to easily connect to DropBox and then access the data inside Power BI.

Read / write DropBox data inside your app; perform many DropBox operations without coding, just use easy to use high performance API Connector for DropBox

Let's follow the steps below to see how we can accomplish that!

Download Documentation

DropBox Connector for Power BI is based on ZappySys API Driver which is part of ODBC PowerPack. It is a collection of high-performance ODBC drivers that enable you to integrate data in SQL Server, SSIS, a programming language, or any other ODBC-compatible application. ODBC PowerPack supports various file formats, sources and destinations, including REST/SOAP API, SFTP/FTP, storage services, and plain files, to mention a few.

Connect to DropBox in other apps

Connect to DropBox in SSIS

Connect to DropBox in SQL Server

Connect to DropBox in SSRS

Connect to DropBox in Informatica

Connect to DropBox in MS Access

Connect to DropBox in MS Excel

Connect to DropBox in SSAS

Connect to DropBox in C#

Connect to DropBox in Python

Connect to DropBox in JAVA

Connect to DropBox in Tableau

Connect to DropBox in SAP Crystal Reports

Connect to DropBox in Azure Data Factory (Pipeline)

Connect to DropBox in Azure Data Factory (SSIS)

Connect to DropBox in Talend Studio

Connect to DropBox in UiPath

Connect to DropBox in PowerShell

Connect to DropBox in ODBC

Video Tutorial - Integrate DropBox 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 DropBox integration in Power BI
How to configure connection for DropBox
Features about API Driver (Authentication / Query Language / Examples / Driver UI)
Using DropBox Connection in Power BI

Watch this video on YouTube

Create ODBC Data Source (DSN) based on ZappySys API Driver

Step-by-step instructions

To get data from DropBox using Power BI we first need to create a DSN (Data Source) which will access data from DropBox. 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 Driver
- Create and use User DSN if the client application is run under a User Account. This is an ideal option in design-time, when developing a solution, e.g. in Visual Studio 2019. Use it for both type of applications - 64-bit and 32-bit.
- Create and use System DSN if the client application is launched under a System Account, e.g. as a Windows Service. Usually, this is an ideal option to use in a production environment. Use ODBC Data Source Administrator (32-bit), instead of 64-bit version, if Windows Service is a 32-bit application.
Power BI uses a Service Account, when a solution is deployed to production environment, therefore for production environment you have to create and use a System DSN.
When the Configuration window appears give your data source a name if you haven't done that already, then select "DropBox" from the list of Popular Connectors. If "DropBox" 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:

DropboxDSN

DropBox
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.
User Account [OAuth]
Steps how to get and use DropBox credentials : User Account [OAuth]

To use OAuth authentication, firstly, you need to create OAuth application:

Log into your DropBox account.

Go to DropBox My Apps.

Then press Create app button to create a new app:

Once a new page opens, select Scoped access option:

Next, select Full Dropbox to access all files and folders or App folder to access specific folder's files and folders option.

Continue by giving your app a name.

Then check I agree to Dropbox API Terms and Conditions checkbox.

Click Create app button.

Once a new page opens, click Enable additional teams and Enable additional users buttons:

Then copy App key and App secret and copy paste them into your favorite text editor (you will need them later).

Proceed by setting a Redirect URI and clicking Add button.
NOTE: If you don't have a working Redirect URI, you can use https://zappysys.com/oauth (it's safe).

Then click on Permissions tab and select application scopes:

Select all Individual Scopes and Team Scopes if you want to manage team data.

Click Submit button.

Now go to SSIS package or ODBC data source and in User Account authentication set these parameters:

For ClientId field use App key value.

For ClientSecret field use App secret value.

For ReturnUrl field use Redirect URI value.
Done! Now you are ready to use Dropbox Connector!

NOTE: If you are planning to use your current data connection/token for automated processes, we recommend that you use a generic account for token generation when the login box appears (e.g. sales_automation@mycompany.com instead of bob_smith@mycompany.com). When you use a personal account which is tied to a specific employee profile and that employee leaves the company, the token may become invalid and any automated processes using that token will fail. Another potentially unwanted effect of using a personal token is incorrect logging; the API calls (e.g. Read, Edit, Delete, Upload) made with that token will record the specific user as performing the calls instead of an automated process.

Fill in all required parameters and set optional parameters if needed:

DropboxDSN

DropBox

User Account [OAuth]

https://api.dropboxapi.com/2/

Required Parameters
UseCustomApp	Fill-in the parameter...
ReturnUrl	Fill-in the parameter...
Optional Parameters
ClientId
ClientSecret
Scope
RetryMode	RetryWhenStatusCodeMatch
RetryStatusCodeList	429
RetryCountMax	5
RetryMultiplyWaitTime	True

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

Watch this video on YouTube

Read DropBox data in Power BI using ODBC

Importing DropBox data into Power BI from table or view

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 DropboxDSN and continue:

DropboxDSN
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:

DropboxDSN
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 DropBox in a Power BI report:

Importing DropBox data into Power BI using SQL query

If you wish to import DropBox data from SQL query rather than a table 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.

DropboxDSN

                SELECT
                    ProductID,
                    ProductName,
                    SupplierID,
                    CategoryID,
                    QuantityPerUnit,
                    UnitPrice
                FROM Products
                WHERE UnitPrice > 20

Get REST API data in Power BI Desktop using SQL query and ODBC

Consider using Custom Objects feature in ODBC data source to encapsulate SQL query in a Virtual Table. This way, you can see a virtual table in Power BI table list where you can import multiple objects using the same connection rather than creating a new connection for each custom SQL query.

Using a full ODBC connection string

In the previous steps we used a very short format of ODBC connection string - a DSN. Yet sometimes you don't want a dependency on an ODBC data source (and an extra step). In those times, you can define a full connection string and skip creating an ODBC data source entirely. Let's see below how to accomplish that in the below steps:

Open ODBC data source configuration and click Copy settings:

ZappySys API Driver - DropBox

Read / write DropBox data inside your app; perform many DropBox operations without coding, just use easy to use high performance API Connector for DropBox

DropboxDSN
The window opens, telling us the connection string was successfully copied to the clipboard:
Then just paste the connection string into your script:

DropboxDSN

DRIVER={ZappySys API Driver};ServiceUrl=https://api.dropboxapi.com/2/;Provider=DropBox;ExtraAttributesForAuthRequest=token_access_type=offline;ScopeSeparator={space};ReturnUrl=[$ReturnUrl$]
You are good to go! The script will execute the same way as using a DSN.

The DSN defined in the Data source name (DSN) field will be ignored.

Have in mind that a full connection string has length limitations.

Proceed to the next step to find out the details.

Limitations of using a full connection string

Despite using a full ODBC connection string may be very convenient it comes with a limitation: it's length is limited to 1024 symbols (or sometimes more). It usually happens when API provider generates a very long Refresh Token when OAuth is at play. If you are using such a long ODBC connection string, you may get this error:

"Connection string exceeds maximum allowed length of 1024"

But there is a solution to this by storing the full connection string in a file. Follow the steps below to achieve this:

Open your ODBC data source.
Click Copy settings button to copy a full connection string (see the previous section on how to accomplish that).
Then create a new file, let's say, in C:\temp\odbc-connection-string.txt.
Continue by pasting the copied connection string into a newly created file and save it.
Finally, the last step! Just construct a shorter ODBC connection string using this format:
```
DRIVER={ZappySys API Driver};SettingsFile=C:\temp\odbc-connection-string.txt
```
Our troubles are over! Now you should be able to use this connection string in Power BI with no problems.

This feature requires ODBC PowerPack v1.9.0 or later.

Editing query for table in Power BI

There will be a time you need to change the initial query after importing data into Power BI. Don't worry, just right-click on your table and click Edit query menu item:

Edit query in Power BI to get REST API data

Refer to Power Query M reference for more information on how to use its advanced features in your queries.

Using parameters in Power BI (dynamic query)

In the real world, many values of your REST / SOAP API call may be coming from parameters. If that's the case for you can try to edit script manually as below. In below example its calling SQL Query with POST method and passing some parameters. Notice below where paraAPIKey is Power BI Parameter (string type). You can use parameters anywhere in your script just like the normal variable.

To use a parameter in Power BI report, follow these simple steps:

Firstly, you need to Edit query of your table (see previous section)

Then just create a new parameter by clicking Manage Parameters dropdown, click New Parameter option, and use it in the query:

						
                            = Odbc.Query("dsn=DropboxDSN",
                                         "SELECT ProductID, ProductName, UnitPrice, UnitsInStock
                                          FROM Products
                                          WHERE UnitPrice > " & Text.From(MyParameter) & "
                                          ORDER BY UnitPrice")

Use parameter in Power BI to get REST API data

Refer to Power Query M reference for more information on how to use its advanced features in your queries.

Using DirectQuery Option rather than Import

So far we have seen how to Import DropBox data into Power BI but what if you have too much data and you don't want to import but link it. Power BI Offers very useful feature for this scenario. It's called DirectQuery Option. In this section we will explore how to use DirectQuery along with ZappySys Drivers.

Out of the box ZappySys Drivers won't 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 DropBox 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, then issue OPENROWSET queries from Power BI to SQL Server, and it will then call DropBox via ZappySys Data Gateway.

First, create a data source in ZappySys Data Gateway and create a Linked Server based on it.
Once SQL Server Linked Server is configured we are ready to issue a SQL 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 DropBox Data Source in Data Gateway and defined linked server (Change name below).
```
SELECT * FROM OPENQUERY([LINKED_SERVER_TO_DROPBOX_IN_DATA_GATEWAY], 'SELECT * FROM Customers')
```
SELECT * FROM OPENQUERY([LINKED_SERVER_TO_DROPBOX_IN_DATA_GATEWAY], 'SELECT * FROM Customers')

DirectQuery option for Power BI (Read DropBox Data Example using SQL Server Linked Server and ZappySys Data Gateway)
Click OK and Load data... That's it. Now your DropBox API data is linked rather than imported.

Publishing Power BI report to Power BI service

Here are the instructions on how to publish a Power BI report to Power BI service from Power BI Desktop application:

First of all, go to Power BI Desktop, open a Power BI report, and click Publish button:
Then select the Workspace you want to publish report to and hit Select button:
Finally, if everything went right, you will see a window indicating success:

If you need to periodically refresh Power BI semantic model (dataset) to ensure data accuracy and up-to-dateness, you can accomplish that by using Microsoft On-premises data gateway. Proceed to the next section - Refreshing Power BI semantic model (dataset) using On-premises data gateway - and learn how to do that.

Refreshing Power BI semantic model (dataset) using On-premises data gateway

Power BI allows to refresh semantic models which are based on data sources that reside on-premises. This can be achieved using Microsoft On-premises data gateway. There are two types of On-premises gateways:

Standard Mode
Personal Mode

Standard Mode supports Power BI and other Microsoft Data Fabric services. It fits perfectly for Enterprise solutions as it installs as a Windows Service and also supports Direct Query feature.

Personal Mode, on the other hand, can be configured faster, but is designed more for home users (you cannot install it as a Windows Service and it does not support DirectQuery). You will find a detailed comparison in the link above.

We recommend to go with Personal Mode for a quick POC solution, but use Standard Mode in production environment.

Below you will find instructions on how to refresh semantic model using both types of gateways.

Refresh using On-premises data gateway (standard mode)

Here are the instructions on how to refresh a Power BI semantic model using On-premises data gateway (standard mode):

Go to Power BI My workspace, hover your mouse cursor on your semantic model and click Settings:
If you see this view, it means you have to install On-premises data gateway (standard mode):
Install On-premises data gateway (standard mode) and sign-in:

Use the same email address you use when logging in into Power BI account.
Register a new gateway (or migrate an existing one):
If you are creating a new gateway, name your gateway, enter a Recovery key, and click Configure button:
Now, let's get back to your semantic model settings in Power BI portal. Refresh the page and you should see your newly created gateway. Click arrow icon and then click on Add to gateway link:

ODBC{"connectionstring":"dsn=DropboxDSN"}
Once you do that, you will create a new gateway connection. Give it a name, set Authentication method, Privacy level, and click Create button:

dsn=DropboxDSN

In this example, we used the least restrictive Privacy level.

If your connection uses a full connection string you may hit a length limitation when entering it into the field. To create the connection, you will need to shorten it manually. Check the section about the limitation of a full connection string on how to accomplish it.

On-premises data gateway (personal mode) does not have this limitation.
Proceed by choosing the newly created connection:

ODBC{"connectionstring":"dsn=DropboxDSN"}
Finally, you are at the final step where you can refresh the semantic model:

Refresh using On-premises data gateway (personal mode)

Here are the instructions on how to refresh a Power BI semantic model using On-premises data gateway (personal mode):

Go to Power BI My workspace, hover your mouse cursor on your semantic model and click Settings:
If you see this view, it means you have to install On-premises data gateway (personal mode):
Install On-premises data gateway (personal mode) and sign-in:

Use the same email address you use when logging in into Power BI account.
Again, go to your semantic model Settings, expand Data source credentials, click Edit credentials, select Authentication method together with Privacy level, and then click Sign in button:

dsn=DropboxDSN
Finally, you are ready to refresh your semantic model:

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([LINKED_SERVER_TO_DROPBOX_IN_DATA_GATEWAY], '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([LINKED_SERVER_TO_DROPBOX_IN_DATA_GATEWAY], '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 DropBox Connector

DropBox 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.

Make connection test

Makes a connection test [ Read more... ]

List folder

Lists folder [ Read more... ]

Parameter

Description

Path

Recursive

Option	Value
true	true
false	false

Download a file

Downloads a file [ Read more... ]

Parameter	Description
SourceFilePath

Download a folder and folders/files within as ZIP archive

Downloads a folder with all the files and folders it contains as ZIP file [ Read more... ]

Parameter	Description
SourcePath

Upload a file

Upload a file [ Read more... ]

Parameter	Description
TargetFilePath	Specify a file path in DropBox to save file to
SourceFilePath	Specify a disk file path to upload

Create folder

Creates folder [ Read more... ]

Parameter	Description
Path

Delete

Deletes file or folder [ Read more... ]

Parameter	Description
Path

Generic Request

This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [ Read more... ]

Parameter

Description

Url

API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains

Body

Request Body content goes here

IsMultiPart

Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle

Filter

Enter filter to extract array from response. Example: $.rows[*] --OR-- $.customers[*].orders[*]. Check your response document and find out hierarchy you like to extract

Option	Value
No filter
Example1	$.store.books[*]
Example2 (Sections Under Books)	$.store.books[].sections[]
Example3 (Equals)	$.store.books[?(@author=='sam')]
Example4 (Equals - Any Section)	$..[?(@author=='sam')]
Example5 (Not Equals - Any Section)	$..[?(@author!='sam')]
Example6 (Number less than)	$.store.books[?(@.price<10)] Example7 (Regular Expression - Contains Pattern)=$.store.books[?(@author=~ /sam\|bob/ )]
Example8 (Regular Expression - Does Not Contain Pattern)	$.store.books[?(@author=~ /^((?!sam\|bob).)*$/ )]
Example9 (Regular Expression - Exact Pattern Match)	$.store.books[?(@author=~ /^sam\|bob$/ )]
Example10 (Regular Expression - Starts With)	$.store.books[?(@author=~ /^sam/ )]
Example11 (Regular Expression - Ends With)	$.store.books[?(@author=~ /sam$/ )]
Example12 (Between)	$.store.employees[?( @.hiredate>'2015-01-01' && @.hiredate<'2015-01-04' )]

Headers

Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair

Generic Request (Bulk Write)

This is a generic endpoint for bulk write purpose. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [ Read more... ]

Parameter	Description
Url	API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
IsMultiPart	Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter	Enter filter to extract array from response. Example: $.rows[] --OR-- $.customers[].orders[*]. Check your response document and find out hierarchy you like to extract
Headers	Headers for Request. To enter multiple headers use double pipe (\|\|) or new line after each {header-name}:{value} pair

DropBox 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.

Test connection [ Read more... ]

Tests connection

SELECT *
  FROM make_test

List folder #1 [ Read more... ]

Lists all files and folders within a folder

SELECT *
  FROM list_folder

List folder #2 [ Read more... ]

Lists all files and folders within a folder

SELECT *
  FROM list_folder
  WITH (Path='/MySubfolder'
       ,Recursive='true')

Download file [ Read more... ]

Downloads a file

SELECT *
  FROM download_file
  WITH (SourceFilePath='/file-I-want-to-download.dat'
        ,ResponseDataFile='C:\path\I\want\to\save\my\file\to.dat'
      )

Download folder as ZIP file [ Read more... ]

Downloads a folder with all files and folders within it as ZIP file

SELECT *
  FROM download_folder
  WITH (SourcePath='/folder-I-want-to-download'
        ,ResponseDataFile='C:\path\I\want\to\save\my\folder\to.zip'
      )

Upload a file [ Read more... ]

Uploads a file

SELECT *
  FROM upload_file
  WITH (TargetFilePath='/MySubfolder/file-I-want-to-upload-to-dropbox.dat'
        ,DiskFilePath='C:\file\I\want\to\upload.dat'
      )

Delete a file or a folder [ Read more... ]

Deletes a file or a folder

SELECT *
  FROM delete
  WITH (Path='/path/to/file/in/dropbox/I/want/to/delete.dat')

Create a folder [ Read more... ]

Creates a folder

SELECT *
  FROM create_folder
  WITH (Path='/folder/in/dropbox/I/want/to/create')

Conclusion

In this article we showed you how to connect to DropBox in Power BI and integrate data without any coding, saving you time and effort. We encourage you to download DropBox Connector for Power BI and see how easy it is to use it for yourself or your team.

If you have any questions, feel free to contact ZappySys support team. You can also open a live chat immediately by clicking on the chat icon below.

Download DropBox Connector for Power BI Documentation

More integrations

Other connectors for Power BI

Amazon Ads

Amazon Selling Partner (SP-API)

Asana

Azure DevOps

Cosmos DB

ElasticSearch

FastSpring

Google Ads

Google BigQuery

Google Calendar

Google Drive

Google Sheets

Hubspot

Jira

Mailchimp

ManagedEngine ServiceDesk Plus (Zoho)

OData

OneDrive

Outlook Mail (Office 365)

Power BI

ServiceNow

SharePoint Online

Shopify

Smartsheet

Stripe

YouTube

Zendesk

Zoho CRM

Zoho SalesIQ

Zoom

REST API

JSON

JSON File

XML

SOAP

XML File

JDBC-ODBC Bridge

Salesforce

CSV

Amazon S3 JSON File

Amazon S3 XML File

Amazon S3 CSV File

Azure Blob JSON File

Azure Blob XML File

Azure Blob CSV File

FTP/SFTP JSON File

FTP/SFTP XML File

FTP/SFTP CSV File

Build your own Custom API Connector

Other application integration scenarios for DropBox

SSIS

SQL Server

SSRS

Informatica

MS Access

MS Excel

SSAS

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Talend Studio

UiPath

PowerShell

ODBC

Download DropBox Connector for Power BI Documentation

Common Searches:

How to connect DropBox in Power BI?
How to get DropBox data in Power BI?
How to read DropBox data in Power BI?
How to load DropBox data in Power BI?
How to import DropBox data in Power BI?
How to pull DropBox data in Power BI?
How to push data to DropBox in Power BI?
How to write data to DropBox in Power BI?
How to POST data to DropBox in Power BI?
Call DropBox API in Power BI
Consume DropBox API in Power BI
DropBox Power BI Automate
DropBox Power BI Integration
Integration DropBox in Power BI
Consume real-time DropBox data in Power BI
Consume real-time DropBox API data in Power BI
DropBox ODBC Driver | ODBC Driver for DropBox | ODBC DropBox Driver | SSIS DropBox Source | SSIS DropBox Destination
Connect DropBox in Power BI
Load DropBox in Power BI
Load DropBox data in Power BI
Read DropBox data in Power BI
DropBox API Call in Power BI