Canvas app - Ben Prins

Power Platform: Monitoring a power app

24 October 2025 Benjamin Prins Power Platform

When building apps in Power Apps, understanding what happens behind the scenes is essential for smooth performance and reliable functionality. The Monitor tool provides a powerful way to observe your app in action, offering real-time insights into its behavior and interactions.

Monitor acts as a live event viewer, capturing everything from data operations to user-triggered actions. It helps makers identify issues quickly, optimize performance, and validate logic without guesswork. Whether you’re troubleshooting a connector, analyzing load times, or verifying formula execution, Monitor gives you the visibility you need.

With Monitor, you can capture:

Performance metrics (load times, data refresh times)
Function calls (e.g., ClearCollect, Patch, Navigate)
Network requests (to SharePoint, Dataverse, APIs)
Errors and warnings
Trace logs (from Trace() statements)

How to use the monitor tool

In Power Apps Studio, from the app list, select Details → Live monitor under the app’s menu (3 dots).
The Monitor window will open for your app.

Click Play published app to run the app. It will open in a new browser tab.
Use the app as you normally would, focusing on the parts you want to monitor.
Events will appear live in the Monitor window as you interact with the app.
Use filters to narrow down event types such as Errors, Warnings, or Trace messages.
Click any event to view detailed information, including formula execution, data payload, and timing.

How to use Trace()

The Trace function allows you to send custom messages to the Monitor log while your app runs. This is useful for debugging and understanding the flow of your app. You can log simple text messages, variable values, or even complex objects and collections. You can also specify the severity of the message, such as Information, Warning, or Error. Trace is only available in canvas apps and does not work in model-driven apps.

To send a message only when a specific condition is met, wrap the Trace function inside an If statement. This helps you log errors or warnings only when they occur, instead of flooding the log with unnecessary messages.

Trace("Start of OnScreen"); // Manual text message

Trace("Value of varCompHeigh" & varCompHeight); // A variable

Trace("Value of gblAppColors" & JSON(gblAppColors)); // An object as JSON

Trace("Trace Warning", TraceSeverity.Warning); // Trace of type warning

Trace("Trace Critical", TraceSeverity.Critical); // Trace of type Critical

Trace("Trace Error", TraceSeverity.Error); // Trace of type Error

Trace("Trace Information", TraceSeverity.Information); // Trace of type Information

If(IsEmpty(colDesks), Trace("Collection is empty: " & JSON(colDesks), TraceSeverity.Error)) // Trace within If condition

Trace("End of OnStart"); // Manual text message

Power App: Tips & Tricks

10 June 2025 Benjamin Prins Power Platform

Today, we will delve into some practical tips and tricks that can enhance your experience while working with Power Apps. Whether you’re a seasoned developer or just starting out, these tips will help you streamline your workflow and make the most out of the Power Platform.

In this post, we’ll cover various aspects of working with Dataverse forms in canvas apps, including how to handle different form modes, retrieve the last submitted data, and reset variables in SharePoint-integrated Power Apps. Additionally, we’ll explore how to use the concurrent function to load multiple data sources quickly, get current user details, and cache data for better performance.

Form modes

When working with a Dataverse form in a canvas app, you sometimes need different behavior for the edit, new, or view mode of the form. Each mode is represented by a number, and you can use the following code to check the current FormMode. Form2 is the name of the form.

If(Form2.Mode = 0, "Edit", Form2.Mode = 2, "View", "New")

Enum Name	Numeric Value
FormMode.Edit	0
FormMode.New	1
FormMode.View	2

It can also be done by comparing the Mode of the form SharePointForm1.LastSubmit.ID with the FormMode.Edit / View or New code.

If(Form2.Mode = FormMode.Edit, "Edit", Form2.Mode = FormMode.View, "View", "New")

Last submitted data

When working with a form to submit data to Dataverse you can get the last submitted data. You can get the ID of the created record by calling the LastSubmit followed by the name of the ID column.

Form1.LastSubmit.Contact

This can also be done with a SharePoint integration power app by calling the LastSubmit code from the SharePoint form.

SharePointForm1.LastSubmit.ID

Reset variables in SharePoint integrated Power App

When you set variables in a SharePoint integrated Power App don’t forget to reset them when the user closes the app either resetting the variables in the OnCancel or OnSave or resetting them when the form gets opened.

Set(varStatus, Blank());
Set(varFlag, false);

Use concurrent to load multiple sources quicker

When you want to store multiple sources locally, you can load them in a collect one after the other.

ClearCollect(Account, Accounts);
ClearCollect(Contact, Contacts);

But you can also load them in parallel by using the concurrent function. This will load them faster by loading them at the same time.

Concurrent(
    ClearCollect(colAccount, Accounts),
    ClearCollect(colContact, Contacts)
);

Get current users details

You can get the current user’s details by using the User() function.

User().EntraObjectId;
User().Email;
User().FullName;
User().Image;

Cache data that does not change but is used in multiple locations

When you are calling the same function again to access a resource to get the same data it is better (faster) to retrieve it once and store it in a variable.

Set(varCurrentUserName

Set(varUsername, User().FullName);
Set(varMyAccountName, LookUp(Accounts, 'Account Name' = "Contoso, Ltd."));

Drop-down not showing the correct values

Sometimes when you add a drop-down to a canvas app the displayed values are item 1, item 2 etc. Instead of the actual values. This happens when the drop-down list options are not loaded correctly.

Go to the DisplayFields property of the drop-down and set the it to [“Value2”] instead of [“Value”]. The canvas app will see that this is incorrect and change it back to [“Value”] and refresh the drop-down values. Now all the correct values will be visible.

Power Platform: Enhancing SharePoint Integrated Power Apps with Post-Submit Actions

08 May 2025 Benjamin Prins Power Platform

Creating a seamless user experience in a SharePoint integrated Power App (Canvas App) can be challenging, especially when performing actions after form submission. Once a form is submitted, it closes, but the OnSuccess property allows you to run code post-submission.

In this blog, I’ll show you how to use the OnSuccess property to make changes to the newly created SharePoint item. Although you can’t use ThisItem or link directly to data cards, I’ll guide you through the process to ensure your app functions smoothly.

By the end, you’ll know how to enhance your Power App’s functionality and improve user experience. Let’s dive in!

Create a SharePoint list

Create a SharePoint list on any SharePoint site.
Add 1 text column named OnSuccesData.

Create the SharePoint integrated power app.

Open the created SharePoint list.
Click on Integrate, Power Apps, Customize Forms app.
This will create a basic SharePoint integrated power.

Remove the Attachments DataCard.
Click on the SharePointForm1 and add a custom datacard.
Add a label and a Text Input objects on the datacard.
Rename the label to lbl_OnSuccesData.
Rename the Text Input to txt_OnSuccesData.
Set the OnChange to the following code.
- We need to store the Text value in a variable, because when you call directly for txt_OnSuccesData.Text it will work for editing items but not for creating items.

Set(varOnSuccesData, txt_OnSuccesData.Text);

Set the 2 objects below each other.

Set the text of the label to On Succes Data.
Set the Default of the text input to “”.

Create a new blank Power Automate flow from the power app.
Name the flow to Actions after submission.
Set the following text inputs.
- ItemID
- OnSuccesData

Add the SharePoint action Update item and set it for the earlier created SharePoint list.
Set the Id to ItemID from the power app.
Set On Succes Data to OnSuccesData from the power app.
Save the Power Automate flow.
Open the Power App again.
Select the OnSuccess property of the SharePointForm1 object.
Add before the ResetForm(Self); code the following code to start the Power Automate flow.

Actionsaftersubmission.Run(SharePointForm1.LastSubmit.ID, varOnSuccesData);

Test your app by putting a text in the title and a text in the second On Succes Data text input object.
After you save the form, the flow will start and store the On Succes Data in the SharePoint on success data column.

Power Platform: QR Codes in a Canvas App

24 March 2025 Benjamin Prins Power Platform

Creating QR codes in a canvas app can significantly enhance user experience by providing quick access to links and information. QR Codes are the way to go if you want to share a link from a canvas app. In this blog, I will explore two efficient methods to generate QR codes: using the QR Code connector and an open source API, both options use the goqr.me API endpoint. These approaches will help streamline the process and offer flexibility in implementation, catering to various business needs.

Methode 1: Using the QR Code connector

This method utilizes the GoQR (Independent Publisher) connector available in Power Apps to generate QR codes effortlessly.

Create a new blank canvas app.
Click on the Data tab and search for QR Code.
Click on the GoQR (Independent Publisher).

Then click on GoQR (Independent Publisher) to add the connection.

Add a Text input.
Add a button, name the button Create QR Code.
Set the OnSelect of the Create QR Code button to the following code.

Set(QRCode, 'GoQR(IndependentPublisher)'.Create(TextInput1.Text))

Add another button, name the button Reset QR Code.
Set the OnSelect of the Reset QR Code button to the following code.

Set(QRCode, Blank())

Add an image object.
Set the image property to the following code.

QRCode

Type an URL in the text input and click on Create QR Code to generate the QR Code.
Click on the Reset QR Code button to reset the QR Code.

Methode 2: Generating QR Code via a direct API call

For users who prefer a more direct approach, it is possible to call the goqr.me API directly from Power Apps. This method is flexible and does not require adding a connector.

Create a new blank canvas app.
Add a Text input.
Add a button, name the button Create QR Code.
Set the OnSelect of the Create QR Code button to the following code.
Make sure the name of the text input is correct.

Set(QRCode, "https://api.qrserver.com/v1/create-qr-code/?size=150x150&data=" & TextInput2.Text)

Add another button, name the button Reset QR Code.
Set the OnSelect of the Reset QR Code button to the following code.

Set(QRCode, Blank())

Add an image object.
Set the image property to the following code.

QRCode

Type an URL in the text input and click on Create QR Code to generate the QR Code.
Click on the Reset QR Code button to reset the QR Code.

Power Apps: Hidding and showing a component

16 August 2024 Benjamin Prins Power Platform

I was tasked with developing a canvas app for a client that required each screen to include a popup element. The popup needs be openend by clicking an image, upon being clicked, it triggers a popup screen where users can compose a message. I utilized a Library Component and explored methods to control its visibility effectively. The challenge was ensuring that the message popup would appear when an image is clicked and disappear upon user interaction with a designated button. My solution involved manipulating the component’s dimensions — adjusting the height and width to expose only the image or to reveal the entire component. This technique successfully creates the perception of the popup screen being opened and closed by the user.

The first step is to create a solution with a canvas app and a component library.
In my example I named the component comp VIM Message.
Then open the component.
Set the size of the component to 640 by 640.
Add two custom output properties to the component named CompVIMHeigt and CompVIMWidth.

Set the component width to ‘comp VIM Message’.CompVIMWidth
Set the component height to ‘comp VIM Message’.CompVIMHeight
Set the component reset to Set(varCompHeight, 80);
Add an image element and set the following code on the Onselect. This will make the container visible and make the component bigger.

Set(varComVIMVisible, true);
Set(varCompHeight, 640);
Set(varCompWidth, 640);

You might need to adjust the numbers based on your needs.
Also set the X and Y properties on your image based on your needs. I use the following.

X = 'comp VIM Message'.Width - 55
Y = 15

Add a container with the element you need in the popup.
Set the following properties of the container.

Visible = varComVIMVisible
Height = 440
Width = 520
X = 75
Y = 190
Visible = varComVisible

Add two buttons in the container one called Cancel (in Dutch that would be Annuleren) and Send (in Dutch that would be Verzenden).
Set for both button the onselect to the following code, this will make the component smaller and hide the container.

Set(varCompHeight, 80);
Set(varCompWidth, 60);
Set(varComVIMVisible, false);

Open the canvas app and add the component comp CIM Message.
Insert the component into the canvas app.
Set the Heigth property to the following code. This will make sure the Height has a value when the canvas app page is loaded.

If(IsBlank('comp VIM Message_HS'.CompVIMHeight), 80, 'comp VIM Message_HS'.CompVIMHeight)

Set the Width property to the following code. This will make sure the Width has a value when the canvas app page is loaded.

If(IsBlank('comp VIM Message_HS'.CompVIMWidth), 60, 'comp VIM Message_HS'.CompVIMWidth)

Set the X property to the following code. This will make sure that the Image part of the component is on the left top side of the screen.

If('comp VIM Message_HS'.CompVIMWidth = 640, 'Home Screen'.Width - 640, 'Home Screen'.Width - 60)

Now run the canvas app and see if it works (it might not work in the play function in the edit mode).

From Bing Maps to Azure Maps

18 June 2024 Benjamin Prins Power Platform

Bing maps has been an easy-to-use solution for getting location information in canvas apps, but this offering will be placed under the Azure Maps umbrella. While Bing Maps will continue to function for now, it’s essential to prepare for the transition. In this blog post I will explain how to use Azure Maps in a Canvas App. Please note that the locations shown in this post are not my actual location.

Azure Maps Services

First, we need to create a Azure Maps Account in a resource group (I will presume you know how to create a resource group).
Open your resource group.
Click on Create and search for and click on Azure Maps.

Click on Create.
Give the Azure Maps Account resource a name.
Select the correct Region and Pricing tier.
Agree with the terms and click on Review + Create.

Click on Create and wait for the deployment to be ready.
Click on Go to resource.
Click on Authentication and copy the Primary Key. You will need this in the Power Automate Flow.

The Power Automate Flow

Create a new Power Automate Flow and name it Azure maps get Postal Code.
Add as the trigger Power Apps (V2), with two text inputs called Longtitude and Latitude.

Next, we will add a HTTP action, this will call Azure Maps to get the location details based on the provided GPS location.
Set the method to Get.
Set the URI to the following code, make sure to put in your subscription-key (that is the primary key from the Azure Maps Account resource).
Set the Latitude and Longitude with the input fields form the trigger.

https://atlas.microsoft.com/search/address/reverse/json?api-version=1.0&subscription-key={YOUR KEY}&query={Latitude},{Longitude}

Add the action Parse JSON and give it the name Parse JSON – Location information.
Set the Content to the body of the HTTP call and set the schema as detailed in the linked file.

Azure-Maps-JSON-Schema Download

Add a compose action (if you want to only return the first found postal code).
The code for the input is as follows if you have named the Parse JSON action the same as I did.

first(body('Parse_JSON_-_Location_information')?['addresses'])?['address']?['postalCode']

Add the Respond to a Power App or flow action.
Add an output text called postalcode and add the compose as its value.

Your flow will now look like this.

The canvas app

We will now create the canvas app with a map that shows the user’s current location on a map, and a button to get the postal code of that location and a reset button. Please note this is not my actual location.

Create a new canvas app, I blank Phone canvas.
Click on Power Automate followed by Add flow to add the earlier created flow.
Add the map element to the canvas app.
Set the DefaultLatitude property with the following code.

Location.Latitude

Set the Location.Latitude property with the following code.

 Location.Longitude

Set DefaultLocation property with the following code.

true

If you want to see your Latitude and Logitude you can add labels to display the values.
Add a Label and set the Text property with the following code.

"Latitude: " & Location.Latitude

Add a Label and set the Text property with the following code.

"Longitude: " & Location.Longitude

Add a button and set the Text property with the following code.

"Get postal code"

Set following code on the OnSelect property. If needed update the code with your flow name, I used AzuremapsgetPostalCode.

Set(varPostalCode,AzuremapsgetPostalCode.Run(Location.Longitude, Location.Latitude));

Add a button and set the Text property with the following code.

"Reset"

Set following code on the OnSelect property.

Set(varPostalCode, Blank())

Add a label and set the Text property with the following code.

"Postal Code: " & varPostalCode.postalcode

Power Platform and Chat GPT

02 March 2023 Benjamin Prins Power Platform

In today’s digital age, businesses are constantly looking for ways to streamline their processes and improve their customer experience. One way to do this is by leveraging the power of chatbots, which can quickly and efficiently answer customer inquiries. In this blog post, we will explore how to create a canvas app that uses Power Automate flow to ask ChatGPT API questions and display the response in the canvas app. By the end of this tutorial, you will have the tools and knowledge to build your own chatbot app that can answer your customers’ questions in real-time, enhancing their overall experience and increasing your operational efficiency. So, let’s get started!

Create a Chat GPT Api secret

Open the ChatGPT API site.
Login or create an account.
Click on Personal, followed by View API keys.

Click on Create new secret key and save the key in a password vault.

Creating the Power Automate Flow

Create a new Power Automate flow with the name Canvas app – Chat GPT.
Add as the trigger a PowerApps V2.
Add a text input with the name Question.

Add a HTTP action with the name Post to Chat GPT.
Set the Method to POST.
Set the URI to https://api.openai.com/v1/completions.
Set the header to Content-Type with value application/json.
Set a second header to Authorization with the value Bearer [API Secret].
Set the body to the following json code.

{
  "model": "text-davinci-003",
  "prompt": "triggerBody()['text']",
  "temperature": 0,
  "max_tokens": 4000
}

Add a Parse JSON action with the name Chat GPT Response.
Set the Content to Body (response of the HTTP call).
Set the following schema (update the schema is the response is different).

{
    "type": "object",
    "properties": {
        "id": {
            "type": "string"
        },
        "object": {
            "type": "string"
        },
        "created": {
            "type": "integer"
        },
        "model": {
            "type": "string"
        },
        "choices": {
            "type": "array",
            "items": {
                "type": "object",
                "properties": {
                    "text": {
                        "type": "string"
                    },
                    "index": {
                        "type": "integer"
                    },
                    "logprobs": {},
                    "finish_reason": {
                        "type": "string"
                    }
                },
                "required": [
                    "text",
                    "index",
                    "logprobs",
                    "finish_reason"
                ]
            }
        },
        "usage": {
            "type": "object",
            "properties": {
                "prompt_tokens": {
                    "type": "integer"
                },
                "completion_tokens": {
                    "type": "integer"
                },
                "total_tokens": {
                    "type": "integer"
                }
            }
        }
    }
}

Add the Respond to a PowerApp or Flow action.
Add a text output called ChatGPTRepsonse and add the response from Chat GPT with the following code.

first(body('HTTP_-_Post_to_Chat_GPT')?['choices'])?['text']

The overall Power Automate flow will look like this.

Creating the Canvas app

Open the Power Apps Studio and create a new canvas app.
Rename Screen1 to Home.
Add the Canvas app – Chat GPT Power Automate flow to the canvas app.

Add a Rectange Shape to the top of the canvas app with the name RectTitle.
Add a label over the RectTitle with the name lblChatGPT.
Set the Text to “Send your question to the all powerful Chat GPT AI bot”.
Add a label with the name lblGPTRepsonse.
Place the lblGPTRepsonse on the right side of the screen.
Add a text input with the name txtQuestion.
Place the txtQuestion on the left side of the screen.
Set the txtQuestion Default to “What is your question?”.
If you like add an Image with the name imgRobot and add an image of a robot in the Image property.
Place the imgRobot left and next to the lblGPTRepsonse.
Add a button with the name btnSendQuestion.
Set the following code on the Onselect of the btnSendQuestion.
- This will save the response in the variable repsonsegpt.
- Start the flow with the text provided in the textQuestion text input box.

Set(responsegpt, 'Canvasapp-ChatGPT'.Run(txtQuestion.Text).chatgptrespondse)

Create and delete B2C accounts for Dataverse Contact

31 January 2023 Benjamin Prins Power Platform

Today, we’ll be discussing a crucial aspect of B2C account management – the creation and deletion of B2C accounts in response to changes in the Dataverse Contact. This is an important topic for businesses that deal with external Power Pages user (contacts) that want to ensure the security of their records and Power Pages. In this post I will explain how to create or delete B2C accounts that are connected to a Dataverse Contact. So, let’s dive in!

Create a B2C account when a Dataverse Contact is created

Whenever a new contact is created a new B2C account needs to be created automatically that is linked to the contact. This is done thought the email address of the contact and the Azure B2C account id. These automations will limit the amount of manual admin work.

Create a new Power Automate flow with the name Create B2C user for Dataverse Contact.
Add the Dataverse trigger When a row is added.
Set the Change type to Added.
Set the Table name to Contacts.
Set the Scope to Organization.

Create the following 3 variables.

You will need to create an Application Registration in the B2C tenant with the following permissions.

Permission type	Permissions (from least to most privileged)
Delegated (work or school account)	User.ReadWrite.All, Directory.ReadWrite.All
Delegated (personal Microsoft account)	Not supported
Application	User.ReadWrite.All, Directory.ReadWrite.All

Store the Client ID, Tenant ID and Secrect in the corresponding variables.
Add a HTTP action called HTTP – Delete User to the flow.
Set the Method to: Post.
Set the URI to the following code.

https://graph.microsoft.com/v1.0/users

Set the body to the following code.
In my scenario the user will not be using the password but the one-time password from B2C. That’s why I have added a guid twice as the password.
This call will create an account of the type email address which allows for any valid email to be used. The email does not have to be part of the B2C domain.

Parse the JSON response of the HTTP – Create User call.
Add the Dataverse action Update a row.
Set the Table name to Contact.
Set the Row id to the contact id of the trigger.

Add the id that was returned by the HTTP call that created the B2C account.

Save the flow.

Delete B2C account when Dataverse Contact is deleted

In my scenario I am maintaining the Power Pages contacts within a canvas app, and when a contact is deleted the associated B2C account needs to be deleted too.

Create a new Power Automate flow with a Power Apps (V2) trigger with the name Delete B2C users for deleted Dataverse Contact.
Add an input Text field names ActiveDirectoryID.
- This is the Object ID of the Azure B2C Active Directory User connected to the Contact.

Create the following 3 variables.

You will need to create an Application Registration in the B2C tenant with the following permissions .

Permission type	Permissions (from least to most privileged)
Delegated (work or school account)	User.ReadWrite.All
Delegated (personal Microsoft account)	Not supported
Application	User.ReadWrite.All

Store the Client ID, Tenant ID and Secret in the corresponding variables.
Add a HTTP action called HTTP – Delete User to the flow.
Set the Method to: Delete.
Set the URI to the following code.

https://graph.microsoft.com/v1.0/users/

Add the PowerApp (V2) parameter ActiveDirectoryID to the end of the URI.

Set the Tenant, Client ID and Secret fields with their corresponding variables.
Set the Authentication to Active Directory OAuth.
Set the Audience to the following code.

https://graph.microsoft.com

Save the Power Automate Flow.
Open or create a canvas app (Power Apps).
Open the Power Automate panel in the canvas app.
Add the Delete B2C users for deleted Dataverse Contact Power Automate flow.

Add a gallery with the source set to the Dataverse Contact table.
Add a recycle bin or other delete Icon to the gallery.

Add the following code to the recycle bin icon under OnSelect.
- This will remove the contact record.
- Starts the Power Automate Flow and sending the User Name (Users B2C object ID).
- Notifies the users.

Remove(Contacts, ThisItem);
DeleteB2CuserfordeletedDataverseContact.Run(ThisItem.'User Name');
Notify("Record deleted successfully", NotificationType.Success);

Save and publish the canvas app.

Conditional access device filtering for canvas apps

11 August 2022 Benjamin Prins Power Platform

Conditional access policies for individual Power Apps will be general available in September 2022 (currently in public preview) and will give us a lot of control on how users can access Power Apps. With the use of Azure Active Directory Conditional Access, we can add extra layers of security to individual Power Apps to contain sensitive data. In my project we needed to create a conditional access policy to prevent a canvass app being opened on any mobile device. With Conditional access policies for individual Power Apps we were able to do this.

Setting up conditional access

First we need to setup the conditional access policie s in Azure Active Directory and connect it to an authentication context.

Open the authentication context in Azure Active Directory.
Click on New authentication context.
Fill in the Name and Description.
Select Publish to apps.
Select an ID (it does not matter which one).

Open the Policies in Azure Active Directory.
Click on New policy.
Give the policy a name.
Select the users and/or group to apply the policy to

Select the authentication context created earlier.

Create the conditions and select all device platforms besides windows.

Select the Block access under Grant to block all the device platforms besides windows.

Click on Save.
The policy is now created, but still needs to be connected to the canvas app.

Connect the conditional access to the canvass app

The policy needs to be connected to the canvas app with PowerShell.

Open PowerShell as an administrator.
Connect PowerShell to the Power Platform with the following command.

Add-PowerAppsAccount

The PowerShell command requires the EnvironmentName (ID of the environment), AppName (ID of the canvass app) and the ID of the authentication context. The ID’s in my example are changed for security reasons.

Set-AdminPowerAppConditionalAccessAuthenticationContextIds -EnvironmentName Default-44444444-2222-3338-9b7f-0771d0c3301c -AppName b0111111-5555-4444-a22a-5af2574f1ed7 -AuthenticationContextIds c2

The conditional access policy is now connected to the canvas app.

Embed a canvas app in a model-driven app

26 April 2022 Benjamin Prins Power Platform

Did you know that you can embed (add) a canvas app in a model-driven app? With the embedded canvas app, you can fully use the power of the canvas app inside a model-driven app. In my project I used it to provide the user with the capability to search an Oracle database and select a specific company.

It is very easy to add a canvas app, but I recommend to use it only when no other options are viable. The reason for this is that the embedded canvas app needs to be reconnected every time you transfer the solution form one environment to another.

Embed the canvas app

Create / add a canvas app in the same environment as the model-driven app.
Open the form of the entity where the canvas app needs to be embedded.
Click on +Component and select the Canvas app.

Fill in the App ID Static value with the unique ID of the canvas app and click on Done.
You can find the App ID by right clicking on an app and clicking on Details.

Solution deployments

The canvas app is now part of the model-driven app and needs to be in the same solution. When you transfer the solution from the development environment to the test environment, you will need to update the model-driven form manually. The reason for this is that the model-driven app is still connected to the canvas app on development. You will need to change the reference / GUID to the canvass app on production. And do not forget to share the canvas app with the users.