Connect Power Apps to IFS Cloud APIs

Explore this learning path

Documentation-based guide draft · Reviewed against sources on 2026-09-27 · Not executed in an IFS environment. IFS references use 26R1 unless stated otherwise. Confirm available APIs, components, and permissions in your installed release.

Build a small canvas app that reads an approved IFS endpoint through a custom connector. The finished app has a Refresh button, a list, and a visible error message. Start read-only so you can prove identity and data scope before adding updates.

Before you start

You need a Power Apps environment with custom-connector entitlement, permission to create a solution, an HTTPS API reachable from Power Platform, and one successful read under the intended identity. Follow API discovery and authentication first.

Choose one entity collection with a small $select and $top=10. Record the exact response shape. The example assumes an OData JSON response containing a value array; use your API’s shape if it differs.

1. Create the connector in a solution

1. Open Power Apps, select the development environment, and open Solutions.
2. Create or open an unmanaged solution for the exercise.
3. Create a Custom connector → Create from blank, named IFSReadDemo.
4. In General, select HTTPS. Enter the host without https:// and put the stable projection path in Base URL. For a gateway, use its approved host and base path instead.
5. Give the connector a description naming the data it reads and the environment it targets.

Do not place the access token in the URL, connector name, or default header definition.

2. Configure connection authentication

In Security, select the authentication scheme actually supported by the approved endpoint. For delegated IFS OAuth, use the generic OAuth provider settings agreed with your IAM administrator: client ID, confidential client secret where required, authorization URL, token URL, and scopes. Create/update the connector to obtain its generated redirect URL, then register that exact URL on the custom IAM client and reconnect.

This is a user authorization-code connection, not a place to select client credentials for an unattended service account. If your organization uses a service-backed gateway, its API owner must implement caller authorization and document the connector’s authentication contract. Do not put a powerful service secret in a canvas app formula.

Checkpoint: creating a connection opens the expected sign-in flow and returns to Power Apps without a redirect URI error.

3. Define and test one read operation

1. In Definition, add an action. Set its operation ID to ListDemoRecords.
2. Select Import from sample, choose GET, and paste the successful read URL.
3. Define only the query parameters the app needs. Set conservative defaults for row count and selected fields.
4. In the response section, import a sanitized sample response containing two fictional rows so the connector exposes the value array and field types.
5. Save/update the connector. In Test, create a connection and run ListDemoRecords.

Expected result: HTTP 200 with records the connection user is allowed to read. Fix connector authentication, query syntax, or permissions here before debugging the app.

4. Add the connector to a canvas app

Create a blank canvas app in the solution. Add IFSReadDemo through Data, insert a button labelled Refresh, and set its OnSelect formula to:

IfError(
    ClearCollect(ifsRows, IFSReadDemo.ListDemoRecords().value),
    Notify("Could not load IFS records. Check the connection.", NotificationType.Error)
)

This formula assumes a no-argument operation with defaults defined in step 3. If you made parameters required, use the argument names shown by Power Apps IntelliSense. Locale settings may use different formula separators.

Insert a vertical gallery and set Items to ifsRows. Set a gallery label to ThisItem. followed by an actual text field offered by IntelliSense. Do not copy an example field name that your projection does not expose.

5. Test as the person who will use it

Save, publish, and share the app and connector as required by your environment. Have a second authorized user create their own connection and press Refresh. Compare visible business scope with that user’s IFS access. Also test an expired connection, no matching rows, and a denied operation.

If the button works but the list is blank, inspect the connector response and gallery Items formula. If the connector works only for its maker, check sharing, connection creation, and per-user IAM grants. Document the successful user role and query before adding writes. Remove the test app, connector, and custom IAM client when retiring the exercise.

See Microsoft’s custom connector wizard for the current editor screens.

Sources and scope

• Microsoft custom connector lifecycle
• Use a custom connector in Power Apps

Older IFS Applications examples are historical context, not evidence of Cloud compatibility. No third-party code, screenshots, or downloadable workflows are reproduced.