![]() |
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 Act CRM, 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 Act CRM -- this article shows how to use these formulas to connect your PowerApp to remote Act CRM 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 Act CRM OData services:
To work with Act CRM data from Microsoft Power Apps, we start by creating and configuring a Act CRM connection. Follow the steps below to configure the API Server to connect to Act CRM data:
The and properties, under the Authentication section, must be set to valid Act! user credentials. In addition to the authentication values, see the following:
Connecting to Act! Premium
In addition to the authentication values, the to Act! is also required; for example https://eup1-iis-04.eu.hosted.act.com/.
Additionally, you must specify the you will connect to. This is found by going to the About Act! Premium menu of your account, at the top right of the page, in the ? menu. Use the Database Name in the window that appears.
Connecting to Act! Premium Cloud
To connect to your Act! Premium Cloud account, you also need to specify the property. This property is found in the URL address of the Cloud account; for example https://eup1-iis-04.eu.hosted.act.com/ActCloudName/.
Note that retrieving ActCRM metadata can be expensive. It is advised that you set the property to store the metadata locally.
π Connecting to a datasource (SQLite is shown)Next, create a user to access your Act CRM 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 Act CRM tables:
Having configured a connection to Act CRM 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 Act CRM data.
Follow the steps below to connect to Act CRM from a Power App:
Follow the steps below to create a simple app that can search Act CRM data. You will use Power Apps formulas to bind Act CRM 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 Act CRM data on the Advanced tab of the gallery settings. The formula below will allow you to access columns in the Activities table.
ForAll(CDataSwaggerAPI.getAllActivities().value, {myActivityDisplayName: ActivityDisplayName, mySubject: Subject})
Assign Act CRM columns to UI elements by clicking the element and then setting the Text property (on the Advanced tab of the UI element) to ThisItem.myActivityDisplayName or ThisItem.mySubject.
π 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.getAllActivities().value, {myActivityDisplayName: ActivityDisplayName, mySubject: Subject}),
ForAll(CDataSwaggerAPI.getAllActivities({'$filter':Concatenate("contains(ActivityDisplayName,",TextInput1.Text,")")}).value, {myActivityDisplayName: ActivityDisplayName, mySubject: Subject}))
The formula builds an OData query that the API Server executes against the remote Act CRM 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 Act CRM 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.updateActivities(BrowseGallery.Selected.myId,BrowseGallery.Selected.myId,{ActivityDisplayName:TextInput1.Text,Subject:TextInput2.Text})
Navigate( BrowseScreen, None )
Your mobile or tablet app can now browse, search, and update Act CRM data.
Learn more or sign up for a free trial:
CData API Server