Skip to main content

Embedding FormsPro surveys via a Canvas app

Embedding Canvas apps

Today we will have a look on how to embedd FormsPro surveys into a model driven app, to capture feedback like KYC check, Risk profile or Client Satisfaction surveys for an account.

First we add a new section to our account form, where we add one mandatory field, that will host the canvas app:


Then we double click on that field and navigate to the controls tab. Here we add a new controll of type Canvas app:


After clicking on add, we select this control for the web form (at the moment embedded Canvas apps are not supported in the mobile version) and click on customize to create the app:


Once the Power Apps Studio has launched, we add a new screen, that will be our home page:


As a next step we get rid of the form that has been added by default, since we do not need it in our case:



Now we add a label to our home page, asking the user to select a survey:


Then we add a drop down, where the user can choose the survey:


In the properties of the drop down we select the entity "Forms Pro surveys" in the items property and the field name in the value property:


To launch the survey screen we add a button:


Now we add a new screen and add the "Forms Pro" control:


To open the survey, chosen in the drop down, we enter following formula in the advanced properties of the Forms Pro control:


Now we define the transition for the button, that shall launch the survey:


We are done configuring our Canvas app and define a name for the app and choose an icon:


Next we save and publish the app:


Now the app id is filled out in our custom control in our model driven app:


(I would recomend to also move to tab display and hide the field label, else it would be shown next to the canvas app).

Finally we save and publish our account form in the model driven app:


Time to Test

Lets open one test account and see if our new app is correctly rendered. And here it is:


After clicking on the Fill out button, the chosen survey is rendered:


When the survey is submitted a confirmation page is displayed:


If we navigate to our survey in CRM, the response is shown:


The response is not yet linked to the correct account. For that purpose we would have to pass the context to the survey:


Then we could use this context to personalize the survey or to link the response with the account (e.g. with a flow listening on forms pro responses).

Comments

Popular posts from this blog

Power Automate Get absolute Sharepoint URL from document location

Document Locations If you enable Sharepoint document integration in your model driven apps, you can define for which entities the possibility to upload documents to sharepoint shall be offered and you can define a folder structure. Possible folder structures can either be based on account or contact, which means if you create child items (e.g. opportunities, activities, ...) sub folders are created below. If an entity is enabled for document management a "Files" tab is added to the form of your model driven app and as soon as you click on that tab a folder is automatically generated on Sharepoint. Once the folder has been created you have options to create new or upload existing file or to open the document location (folder) on Sharepoint: What happens behind the scenes is, as soon as you click on the files tab your model driven app checks, weither a "document location" for this item already exists, or not. The document location is an own entity in C

Send e-mails with a link to the record via Power Automate

Today we gonna have a look at how to send an e-mail with a link to a CDS record via Power Automate. In the good old classic workflows, you could directly reference the "record URL" from the dynamic data. But since UCI has been launched and you have the possiblity to target different apps, you already had to do a few more steps in the classic workflows as well. The URL to a CDS record consists of multiple things: CRM URL appid entity name record id So we will work this out one after the other. First we add a "List record" action to lookup the appid of the app, we target. We look for "model driven apps" and filter by the name of the app: Then we initialize a variable with the resulting app id: Then we initialize another variable and extract the CRM_URL: Then we fetch our records, where we want to send out a notification with a link, in this case we look for workorders fullfilling certain criteria: Now we compose the record URL: As a next step we create a new

Working with Optionset lables in Power Automate

Connector Types Power Automate currently offers 3 different connectors, to connect Power Automate with your Dynamics 365 instance: Dynamics 365 Common Data Service Common Data Service (current environment) Today we will look on ways how to retrieve option set labels via the different connectors, for our sample accounts: Dynamics 365 This connector should not be used any more , since in April 2019 it has been announced as being deprecated. https://flow.microsoft.com/en-us/blog/nine-new-connectors-in-april-and-improved-visibility-into-trigger-failures/ With the Dynamics 365 connector it was quite easy to work with optionsets, since it offered both the optionset value (int) and the optionset label (name) in the dynamic content: And here we go, these are our results: Common Data Service Since the Dynamics 365 connector has been deprecated, this is the connector you should use. If you perform a "Get record" or "List records&