![]() |
VOOZH | about |
Microsoft Power Apps provides a drag and drop interface, underpinned by a rich set of formulas, for generating mobile and tablet apps that are connected to data. The CData API Server extends Power Apps with connectivity to remote data sources, without a need to maintain a separate copy of the data in the Power Apps Common Data Service. The CData API Server provides database-like connectivity for BigQuery, augmenting the functionality of SaaS APIs and NoSQL databases with an in-memory SQL-92 engine.
The CData API Server also supports the Swagger metadata standard, whose UI-generation and code-generation possibilities are utilized across Azure App Service, Power Automate, and Power Apps. With Swagger, Power Apps generates a complete set of formulas for working with BigQuery -- this article shows how to use these formulas to connect your PowerApp to remote BigQuery data.
CData simplifies access and integration of live Google BigQuery data. Our customers leverage CData connectivity to:
Most CData customers are using Google BigQuery as their data warehouse and so use CData solutions to migrate business data from separate sources into BigQuery for comprehensive analytics. Other customers use our connectivity to analyze and report on their Google BigQuery data, with many customers using both solutions.
For more details on how CData enhances your Google BigQuery experience, check out our blog post: https://www.cdata.com/blog/what-is-bigquery
If you have not already done so, download the CData API Server. Once you have installed the API Server, follow the steps below to begin producing secure BigQuery OData services:
To work with BigQuery data from Microsoft Power Apps, we start by creating and configuring a BigQuery connection. Follow the steps below to configure the API Server to connect to BigQuery data:
Google uses the OAuth authentication standard. To access Google APIs on behalf of individual users, you can use the embedded credentials or you can register your own OAuth app.
OAuth also enables you to use a service account to connect on behalf of users in a Google Apps domain. To authenticate with a service account, register an application to obtain the OAuth JWT values.
In addition to the OAuth values, specify the DatasetId and ProjectId. See the "Getting Started" chapter of the help documentation for a guide to using OAuth.
π Connecting to a datasource (SQLite is shown)Next, create a user to access your BigQuery data through the API Server. You can add and configure users on the Users page. Follow the steps below to configure and create a user:
Having created a user, you are ready to create API endpoints for the BigQuery tables:
Having configured a connection to BigQuery data, created a user, and added resources to the API Server, you now have an easily accessible REST API based on the OData protocol for those resources. From the API page in API Server, you can view and copy the API Endpoints for the API:
π API EndpointsYou will use the metadata to create a Custom API connection. You can obtain the Swagger definition by making the following request in your browser and then saving the resulting JSON file:
http://MySite:MyPort/api.rsc/$oas?version=2
The following procedure shows how to create a simple app that searches remote BigQuery data.
Follow the steps below to connect to BigQuery from a Power App:
Follow the steps below to create a simple app that can search BigQuery data. You will use Power Apps formulas to bind BigQuery rows to rows in a gallery control.
In the View tab, click Gallery -> Vertical to add a Gallery.
After selecting a gallery, assign the Items property of the gallery to BigQuery data on the Advanced tab of the gallery settings. The formula below will allow you to access columns in the Orders table.
ForAll(CDataSwaggerAPI.getAllOrders().value, {myOrderName: OrderName, myFreight: Freight})
Assign BigQuery columns to UI elements by clicking the element and then setting the Text property (on the Advanced tab of the UI element) to ThisItem.myOrderName or ThisItem.myFreight.
π Adding the connection to the layout.To filter the records displayed by the gallery, add a TextInput to your Screen, clear the Text property for the TextInput, and set the Items property of the gallery to a formula like the one below, replacing TextInput1 with the name of the TextInput control in your gallery, if necessary:
If(IsBlank(TextInput1.Text),
ForAll(CDataSwaggerAPI.getAllOrders().value, {myOrderName: OrderName, myFreight: Freight}),
ForAll(CDataSwaggerAPI.getAllOrders({'$filter':Concatenate("contains(OrderName,",TextInput1.Text,")")}).value, {myOrderName: OrderName, myFreight: Freight}))
The formula builds an OData query that the API Server executes against the remote BigQuery data, ensuring that the search is run against the current data without first pulling in every record into the app. You can find more information on the supported OData in the API Server help documentation.
Follow the steps below to load an editable screen that shows the fields of the BigQuery record selected in the gallery.
Navigate( Details, None )
For each column you will need to do the following. Note that for Custom APIs form elements cannot detect which requests need to be formulated to the API Server, so you will need to write the data modification formulas manually.
To give your app basic update functionality and navigation, add Submit and Back buttons:
CDataSwaggerAPI.updateOrders(BrowseGallery.Selected.myId,BrowseGallery.Selected.myId,{OrderName:TextInput1.Text,Freight:TextInput2.Text})
Navigate( BrowseScreen, None )
Your mobile or tablet app can now browse, search, and update BigQuery data.
Learn more or sign up for a free trial:
CData API Server