{"id":13355,"date":"2016-10-27T00:00:00","date_gmt":"2016-10-27T05:00:00","guid":{"rendered":"https:\/\/centricconsulting.com\/post\/office-365-powerapps-deepish-dive-part-3\/"},"modified":"2021-12-15T00:13:24","modified_gmt":"2021-12-15T05:13:24","slug":"office-365-powerapps-deepish-dive-part-3","status":"publish","type":"post","link":"https:\/\/centricconsulting.com\/blog\/office-365-powerapps-deepish-dive-part-3\/","title":{"rendered":"Office 365 PowerApps Deep(ish) Dive – Part 3"},"content":{"rendered":"

In this series of blogs, we explore the key capabilities in Office 365 and SharePoint to create business solutions, with a primary focus on PowerApps.<\/h2>\n

Instead of listing the functionalities, we help you build a PowerApp.<\/p>\n

Part three\u00a0of a series<\/a>.<\/em><\/p>\n

In our PowerApp, we can now add<\/em> new menus, so now let\u2019s add the ability for the user to be able to view<\/em> them as well!<\/p>\n

So, the first step will be to add a new screen as we did in part two\u00a0of this series. This new screen will be named \u2018View\u2019. Change the layout to match the edit<\/em> screen.<\/p>\n

For the viewscreen, we will be adding three controls: a vertical gallery, and 2 \u2018View Form\u2019 controls. Add them to the screen, and then arrange them so the gallery is on the left, and the view form controls are on the right:<\/p>\n

\"padd3-1\"<\/p>\n

The goal of the view screen will be to allow users to see all of their submitted forms, and then see the details in the form when they click on the name. In order to accomplish this goal, we will first pull all of the current user\u2019s submitted menus into the vertical gallery control.<\/p>\n

Click on the gallery control, and then find the items<\/em> in the formula drop down. \u00a0Change the Formula to: \u00a0Filter(\u2018Menu Form\u2019, User().FullName in Author.DisplayName)<\/strong><\/p>\n

This formula will filter all of the results from the Menu Form list based upon the current user\u2019s full name, and the author\u2019s display name in SharePoint.<\/p>\n

\"padd3-2\"<\/p>\n

By default, three fields will be returned for each card, so delete the two subheading fields, leaving only the heading<\/em>. As you can see below, I\u2019ve also added an arrow next to the heading, which is for aesthetics:<\/p>\n

\"padd3-3\"<\/p>\n

Now that we have our menus, we will connect the first \u2018View Form\u2019 control to the \u2018Menu Form\u2019 data source by changing the items in the formula bar to Gallery1_1.Selected<\/strong> (Note: this should correspond to whatever you named your gallery control to be.<\/em>) Also, we will click the eye next to \u2018Author\u2019, \u2018Created\u2019 and \u2018Form Status\u2019 to show those three fields in this view.<\/p>\n

When that is completed, you will notice that \u2018Author\u2019 and \u2018Forms Status\u2019 are not showing the normal values you would expect to see, but they are showing Microsoft.Azure<\/span> Connector values.<\/p>\n

\"padd3-4\"<\/p>\n

In order to change this, we just need to change the value<\/em> displayed for each of these fields. Right-click next to author<\/em>, and change its value from odata.type<\/span> to DisplayName. You will now see the name of the person who created the menu. (Note: Certain fields may have multiple value types that you can display, i.e email address).<\/p>\n

\"padd3-5\"<\/p>\n

Also, change the value from odata.type<\/span> to form status to \u2018Value\u2019. You should now see the proper displays from both fields. Also, you will notice that when you click the name of a menu in the gallery, the values change for the view control:<\/p>\n

\"padd3-6\"<\/p>\n

Now, we need to connect the final view control. Change the items drop down in the formula bar to Gallery1_1. Selected,<\/strong> and then click on the eye for fields 1-10. The goal of this view will be to show all of the menu items that were submitted, as well as a picture of the item. Add an image to the right-hand side of each card after the fields have been added.<\/p>\n

Your view should show all of the filed names, as well as the ID numbers of all the submitted items. Time to clean this up a bit. First, change all of the labels to correspond to the menu (i.e. Appetizer Choice 1, etc).<\/p>\n

\"padd3-7\"<\/p>\n

Next you will need to unlock and edit the advanced properties of each field. We will want to perform a lookup to the menu item list for each ID number, and then return the title of the item. We will also want each image control to display the image of each menu Item. Edit the advanced properties of each one as shown below:<\/p>\n

\"padd3-8\"<\/p>\n

When each field has been edited, your screen should look similar to the one below:<\/p>\n

\"padd3-9\"<\/p>\n

Now you can also add a \u2018Back\u2019 button the screen, a well as adding a new button on the home screen so that users can navigate to the view screen. Users now have a way to view the status and details of their menus!<\/p>\n

In part four<\/a> of this series, we\u2019ll add a new screen for \u2018Menu Items\u2019\u00a0and demonstrate how we can display and filter data from SharePoint.<\/p>\n","protected":false},"excerpt":{"rendered":"

Read part three of a series on the key capabilities in Office 365 and SharePoint to create business solutions by using PowerApps.<\/p>\n","protected":false},"author":86,"featured_media":25594,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_oasis_is_in_workflow":0,"_oasis_original":0,"_oasis_task_priority":"","_relevanssi_hide_post":"","_relevanssi_hide_content":"","_relevanssi_pin_for_all":"","_relevanssi_pin_keywords":"","_relevanssi_unpin_keywords":"","_relevanssi_related_keywords":"","_relevanssi_related_include_ids":"","_relevanssi_related_exclude_ids":"","_relevanssi_related_no_append":"","_relevanssi_related_not_related":"","_relevanssi_related_posts":"","_relevanssi_noindex_reason":"","footnotes":""},"categories":[1],"tags":[],"coauthors":[],"acf":[],"publishpress_future_action":{"enabled":false,"date":"2024-07-22 09:35:25","action":"change-status","newStatus":"draft","terms":[],"taxonomy":"category"},"_links":{"self":[{"href":"https:\/\/centricconsulting.com\/wp-json\/wp\/v2\/posts\/13355"}],"collection":[{"href":"https:\/\/centricconsulting.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/centricconsulting.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/centricconsulting.com\/wp-json\/wp\/v2\/users\/86"}],"replies":[{"embeddable":true,"href":"https:\/\/centricconsulting.com\/wp-json\/wp\/v2\/comments?post=13355"}],"version-history":[{"count":0,"href":"https:\/\/centricconsulting.com\/wp-json\/wp\/v2\/posts\/13355\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/centricconsulting.com\/wp-json\/wp\/v2\/media\/25594"}],"wp:attachment":[{"href":"https:\/\/centricconsulting.com\/wp-json\/wp\/v2\/media?parent=13355"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/centricconsulting.com\/wp-json\/wp\/v2\/categories?post=13355"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/centricconsulting.com\/wp-json\/wp\/v2\/tags?post=13355"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/centricconsulting.com\/wp-json\/wp\/v2\/coauthors?post=13355"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}