![]() |
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 Adobe Commerce, 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 Adobe Commerce -- this article shows how to use these formulas to connect your PowerApp to remote Adobe Commerce data.
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 Adobe Commerce OData services:
To work with Adobe Commerce data from Microsoft Power Apps, we start by creating and configuring a Adobe Commerce connection. Follow the steps below to configure the API Server to connect to Adobe Commerce data:
Adobe Commerce uses the OAuth 1 authentication standard. To connect to the Adobe Commerce REST API, obtain values for the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties by registering an app with your Adobe Commerce system. See the "Getting Started" section in the help documentation for a guide to obtaining the OAuth values and connecting.
You will also need to provide the URL to your Adobe Commerce system. The URL depends on whether you are using the Adobe Commerce REST API as a customer or administrator.
Customer: To use Adobe Commerce as a customer, make sure you have created a customer account in the Adobe Commerce homepage. To do so, click Account -> Register. You can then set the URL connection property to the endpoint of your Adobe Commerce system.
Administrator: To access Adobe Commerce as an administrator, set CustomAdminPath instead. This value can be obtained in the Advanced settings in the Admin menu, which can be accessed by selecting System -> Configuration -> Advanced -> Admin -> Admin Base URL.
If the Use Custom Admin Path setting on this page is set to YES, the value is inside the Custom Admin Path text box; otherwise, set the CustomAdminPath connection property to the default value, which is "admin".
Next, create a user to access your Adobe Commerce 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 Adobe Commerce tables:
Having configured a connection to Adobe Commerce 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 Adobe Commerce data.
Follow the steps below to connect to Adobe Commerce from a Power App:
Follow the steps below to create a simple app that can search Adobe Commerce data. You will use Power Apps formulas to bind Adobe Commerce 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 Adobe Commerce data on the Advanced tab of the gallery settings. The formula below will allow you to access columns in the Products table.
ForAll(CDataSwaggerAPI.getAllProducts().value, {myName: Name, myPrice: Price})
Assign Adobe Commerce columns to UI elements by clicking the element and then setting the Text property (on the Advanced tab of the UI element) to ThisItem.myName or ThisItem.myPrice.
π 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.getAllProducts().value, {myName: Name, myPrice: Price}),
ForAll(CDataSwaggerAPI.getAllProducts({'$filter':Concatenate("contains(Name,",TextInput1.Text,")")}).value, {myName: Name, myPrice: Price}))
The formula builds an OData query that the API Server executes against the remote Adobe Commerce 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 Adobe Commerce 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.updateProducts(BrowseGallery.Selected.myId,BrowseGallery.Selected.myId,{Name:TextInput1.Text,Price:TextInput2.Text})
Navigate( BrowseScreen, None )
Your mobile or tablet app can now browse, search, and update Adobe Commerce data.
Learn more or sign up for a free trial:
CData API Server