Integrate Live Bitbucket Data into Custom Business Apps Built in Power Apps



Use CData Connect Server to create a virtual SQL Server Database for Bitbucket data and integrate live Bitbucket data into apps built in Microsoft Power Apps.

Power Apps is a service for building and using custom business apps that connect to your data and work across the web and mobile — without the time and expense of custom software development. When paired with CData Connect Server, you get instant access to Bitbucket data from the apps you build using Power Apps. This article shows how to connect to Connect Server from Power Apps and build an app based on live Bitbucket data.

CData Connect Server provides a pure SQL interface for Bitbucket, allowing you to easily integrate with live Bitbucket data in Power Apps — without replicating the data. CData Connect Server looks exactly like a SQL Server database to Power Apps and uses optimized data processing out of the box to push all supported SQL operations (filters, JOINs, etc) directly to Bitbucket, leveraging server-side processing to quickly return Bitbucket data.

Create a Virtual SQL Database for Bitbucket Data

CData Connect Server uses a straightforward, point-and-click interface to connect to data sources and generate APIs.

  1. Login to Connect Server and click Connections.
  2. Select "Bitbucket" from Available Data Sources.
  3. Enter the necessary authentication properties to connect to Bitbucket.

    For most queries, you must set the Workspace. The only exception to this is the Workspaces table, which does not require this property to be set, as querying it provides a list of workspace slugs that can be used to set Workspace. To query this table, you must set Schema to 'Information' and execute the query SELECT * FROM Workspaces>.

    Setting Schema to 'Information' displays general information. To connect to Bitbucket, set these parameters:

    • Schema: To show general information about a workspace, such as its users, repositories, and projects, set this to Information. Otherwise, set this to the schema of the repository or project you are querying. To get a full set of available schemas, query the sys_schemas table.
    • Workspace: Required if you are not querying the Workspaces table. This property is not required for querying the Workspaces table, as that query only returns a list of workspace slugs that can be used to set Workspace.

    Authenticating to Bitbucket

    Bitbucket supports OAuth authentication only. To enable this authentication from all OAuth flows, you must create a custom OAuth application, and set AuthScheme to OAuth.

    Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).

    Creating a custom OAuth application

    From your Bitbucket account:

    1. Go to Settings (the gear icon) and select Workspace Settings.
    2. In the Apps and Features section, select OAuth Consumers.
    3. Click Add Consumer.
    4. Enter a name and description for your custom application.
    5. Set the callback URL:
      • For desktop applications and headless machines, use http://localhost:33333 or another port number of your choice. The URI you set here becomes the CallbackURL property.
      • For web applications, set the callback URL to a trusted redirect URL. This URL is the web location the user returns to with the token that verifies that your application has been granted access.
    6. If you plan to use client credentials to authenticate, you must select This is a private consumer. In the driver, you must set AuthScheme to client.
    7. Select which permissions to give your OAuth application. These determine what data you can read and write with it.
    8. To save the new custom application, click Save.
    9. After the application has been saved, you can select it to view its settings. The application's Key and Secret are displayed. Record these for future use. You will use the Key to set the OAuthClientId and the Secret to set the OAuthClientSecret.
  4. Click Save Changes
  5. Click Privileges -> Add and add the new user (or an existing user) with the appropriate permissions.

Connecting to CData Connect Server

To use Connect Server to integrate Bitbucket data into your Power Apps, you need a new SQL Server connection:

  1. Log in to Power Apps
  2. Click Data -> Connections -> New connection
  3. Select SQL Server
  4. In the connection wizard:

    • Choose to connect directly
    • Set SQL server name to the address of your Connect Server instance (CONNECT_SERVER_URL)
    • Set SQL database name to the name of the virtual Bitbucket database you created earlier (like bitbucketdb)
    • Set the Username and Password and click Create

Building a Data-Centric App for Bitbucket Data

With the connection to Connect Server configured, you are ready to integrate live Bitbucket data into the apps you build in Power Apps.

  1. Log in to Power Apps
  2. Click Create, hover over "Start from data" and click Make this app
  3. Select the SQL Server connection you created
  4. Search for or choose a table to work with
  5. Click Connect
  6. Customize the newly created app just like you would any other, including changing the layout and setting the fields exposed in BrowseScreen, DetailScreen, and EditScreen

At this point, you have an app with read and write access to live Bitbucket data that you can save and publish for use within your organization.

SQL Access to Bitbucket Data from Applications

Now you have a direct connection to live Bitbucket data from Microsoft Power Apps. You can create more connections and apps to drive business — all without replicating Bitbucket data.

To get SQL data access to 200+ SaaS, Big Data, and NoSQL sources directly from your applications, see the CData Connect Server.

Ready to get started?

Learn more or sign up for a free trial:

CData Connect Server