You’re offline. This is a read only version of the page.
57
I am struggling to embed a canvas app into a model driven app.
Generally, I try to follow this process:
https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/embed-canvas-app-in-form
However, I never have the ModelDrivenFormIntegration Object in the App I try to embed.
I really want to start out simple by displaying the name of the "host record" or something to see that it generally works.
Two observations that lead me to believe that something is messed up in the environment or general settings:
First observation:
When I opened the settings in the app I tried to embed, I get the following pop up:
"please turn on improve data source experience and microsoft dataverse views"
I found this page when searching for this message
https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/use-native-cds-connector
However, this is really confusing. It talks about apps designed before 2019 and references settings that I do not find anywhere.
2nd observation:
When I embed the canvas app and I get the box to enter the Entity Name, App Name and App ID, the 'hover' on the information icon on the App Name and App ID says that it would be automatically generated. However, the "Done" button stays greyed out until I add somthing into the two boxes.
I found some dated stuff to switch to classic mode to get the ModelDrivenFormIntegration, but I feel that something general is messed up so that it does not work out of the box.
Any ideas?
@ivan_apps thanks for this.
It worked exactly like this. Important is to click the "Edit" field from within the property pop-up in the classic view.
Now, I am struggling to display the data and hide the placeholder. It is really a erratic journey, requiring a lot of "googling" and workarounds...
Yes it’s not a great experience. I have found phone formats work best for embedding and creating a 3 column tab and putting the app in one column works best.
now for the tricks to get it to work… it took me a while to get this down.
1. The modern UI interface doesn’t do it right. It lets you add an embedded canvas app but not the way the ModelDrivenIntegration will show up. Unless this has improved, ignore the modern UI for this config and go to classic.
2. You must create a placeholder text field. Easy to not do when using modern editor because it doesn’t require it. But it’s necessary! It’s your anchor to the form, so create a text field and call it app_canvasapp1 or something similar. Then use the classic editor to open that field, add the canvas app component and click on the edit button to launch the editor. you’ll now see that integration component and you can save the canvas app. You won’t have to repeat this process to edit in the future, simply open the canvas app from your solution in the modern view.
3. enable improved embedding feature. It helps with the sizing, ensure everything is responsive too. It’s easy to get carried away designing the canvas app and then when you view it within the model driven form… a good portion is cut off. Test your integration regularly.
you should also only have to list the app unique name so that it will still work when deploying to different environments.
#1
stampcoin
17
#2
ankit_singhal
11
Super User 2025 Season 1
#3
mmbr1606
9
Super User 2025 Season 1
Share
Report
All responses (
Answers (
