{"id":26433,"date":"2021-01-14T10:29:25","date_gmt":"2021-01-14T10:29:25","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=26433"},"modified":"2021-01-21T09:10:18","modified_gmt":"2021-01-21T09:10:18","slug":"use-relevance-search-api-in-power-automate-canvas-app-part-2","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2021\/01\/use-relevance-search-api-in-power-automate-canvas-app-part-2\/","title":{"rendered":"Use Relevance Search API in Power Automate & Canvas App – Part 2"},"content":{"rendered":"

Introduction<\/h1>\n

In the previous blog<\/a>, we obtained the response from the Relevance Search API request through Power Automate Flow. In this blog, we will use that response in the Canvas app. We will see how we can leverage the potential of Relevance search in the Canvas app.<\/p>\n

If you are not familiar with how to create Canvas app then you can refer the following article,<\/p>\n

https:\/\/docs.microsoft.com\/en-us\/powerapps\/maker\/canvas-apps\/get-started-test-drive<\/a><\/p>\n

Let us start with creating a new canvas app,<\/p>\n

\u2022 Sign in to https:\/\/make.powerapps.com<\/a> and create a new Canvas app.<\/p>\n

\"canvas<\/a><\/p>\n

\u2022 As we are going to create Canvas app for Dynamics 365 app, we will select the Common Data Service Phone Layout,<\/p>\n

\"common<\/a><\/p>\n

\u2022 In the next screen, we will first add the connection then add the table.<\/p>\n

\"add<\/a><\/p>\n

\u2022 This will create a canvas app with default Browse, Detail and Edit screen. As we are going to work with Contact and lead, we added the screens for Lead and Contact.<\/p>\n

\"create<\/a><\/p>\n

\u2022 We will now add a new screen for the Relevance Search,\u00a0like shown below<\/p>\n

\"add<\/a><\/p>\n

\u2022 We will call Power Automate Flow that we have created in the previous blog<\/a> upon OnSelect of the Search button and upon OnChange of the textbox.<\/p>\n

We will use below expression OnSelect of the button and on OnChange of the textbox.<\/p>\n

\"Relevance<\/a><\/p>\n

This expression will run the \u2018RelevanceSearchAPIFlow\u2019 and will pass the text entered in the TextBox. After successful run, it will store the response in the Collection called \u201cSearchCollection\u201d.<\/p>\n

\u2022 Save and run the App. Enter some text in the Textbox and either click enter or click on the Search Button. In the background, a Power Automate Flow should run successfully and response should get stored in the \u2018SearchCollection\u2019 collection.<\/p>\n

\u2022 To check the collection, click on View -> Collections<\/p>\n

\"collection\"<\/a><\/p>\n

You should see the response added in the collection.<\/p>\n

\"response<\/a><\/p>\n

\u2022 Now we will use this collection to bind to the List control. Select the List control and add the below expression to the Items property,<\/p>\n

\"Relevance<\/a><\/p>\n

Here we are assigning non-empty items from the SearchCollection collection to the List control.<\/p>\n

\"list<\/a><\/p>\n

\u2022 After this, select the List control and add below expression OnSelect property of the control.<\/p>\n

\"Relevance<\/a><\/p>\n

Here we are extracting and setting the GUID of the record that we have in the collection to the \u2018SelectedItemID\u2019 variable.<\/p>\n

\"extracting<\/a><\/p>\n

\u2022 We will now bind the record values to the list item. Select the first label and add below expression,<\/p>\n

\"Relevance<\/a><\/p>\n

Here we are binding the primary field value of the record.<\/p>\n

\"binding<\/a><\/p>\n

Similarly, select the second label and add below expression,<\/p>\n

\"Relevance<\/a><\/p>\n

Here we are binding the Entity logical name to understand the entity type of the record,<\/p>\n

\"entity<\/p>\n

\u2022 Select the \u2018NextArrow\u2019 button and add below expression upon OnSelect property,<\/p>\n

\"Relevance<\/a><\/p>\n

Here we are first setting the GUID of the record to the SelectedItemID variable and then switching the Detail screen based on the Entity logical name. For example, if the entity is Contact, we are navigating the screen to DetailsScreenContact_1 and if the entity is lead, we are navigating to the DetailsScreenLead_1 screen.<\/p>\n

\"advanced\"<\/a><\/p>\n

\u2022 Now select the Detail screen where we will see the details of the record. Add below expression to Item property of the DetailScreen,<\/p>\n

This expression is for the contact screen,<\/p>\n

\"Relevance<\/a><\/p>\n

\"detail<\/a><\/p>\n

Similarly, add expression for other details screen,<\/p>\n

This expression is for the Lead screen,<\/p>\n

\"Relevance<\/a><\/p>\n

\"detail<\/a><\/p>\n

\u2022 Here we have setup the detail screens of lead and contact to show up the record details on click of the Search Results item from Relevance Search Screen.<\/p>\n

Relevance Search screen,<\/p>\n

\"relevance<\/a><\/p>\n

On click of the next arrow button, it will open the appropriate entity record.<\/p>\n

\"lead\"<\/a><\/p>\n

\u2022 You can add entities that you need and you can add fields to show up in the detail screen or the search result.<\/p>\n

This way we can execute the Relevance search API from Canvas App and represent the Search results using List control.<\/p>\n

Conclusion<\/h2>\n

You can use the logic explained in this blog to add Relevance search into your Canvas app.<\/p>\n

Below is the small clip of the working Relevance Search screen,<\/p>\n

https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2021\/01\/RelevanceSearch.44.27_REC.mp4<\/a><\/video><\/div>\n

\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction In the previous blog, we obtained the response from the Relevance Search API request through Power Automate Flow. In this blog, we will use that response in the Canvas app. We will see how we can leverage the potential of Relevance search in the Canvas app. If you are not familiar with how to\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1954,16,19,1913,38,1985],"tags":[1867,1975,2121],"class_list":["post-26433","post","type-post","status-publish","format-standard","hentry","category-canvas-apps","category-dynamics-365","category-dynamics-crm","category-microsoft-power-platform-services","category-microsoft-powerapps","category-power-automate","tag-canvas-app","tag-power-automate","tag-relevance-search-api"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/26433","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=26433"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/26433\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=26433"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=26433"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=26433"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}