Skip to main content
Microsoft logo
Power Apps
    • AI Builder
    • Automate processes
    • Azure + Power Apps
    • Build apps
    • Connect data
    • Pages
    • Take a guided tour
  • Pricing
    • Overview
    • Become a Partner
    • Find a Partner
    • Find partner offers
    • Partner GTM Resources
    • Blog
    • Customer stories
    • Developer Plan
    • Documentation
    • For IT Leaders
    • Roadmap
    • Self-paced learning
    • Webinars
    • App development topics
    • Overview
    • Issues
    • Give feedback
    • Overview
    • Forums
    • Galleries
    • Submit ideas
    • User groups
    • Register
    • ·
    • Sign in
    • ·
    • Help
    Go To
    • Power Apps Community
    • Welcome to the Community!
    • News & Announcements
    • Get Help with Power Apps
    • Building Power Apps
    • Microsoft Dataverse
    • AI Builder
    • Power Apps Governance and Administering
    • Power Apps Pro Dev & ISV
    • Power Apps Portals
    • Connector Development
    • Power Query
    • GCC, GCCH, DoD - Federal App Makers (FAM)
    • Power Platform Integration - Better Together!
    • Power Platform Integrations
    • Power Platform and Dynamics 365 Integrations
    • Community Blog
    • Power Apps Community Blog
    • Galleries
    • Community Connections & How-To Videos
    • Community App Samples
    • Webinars and Video Gallery
    • Canvas Apps Components Samples
    • Kid Zone
    • Emergency Response Gallery
    • Events
    • 2021 MSBizAppsSummit Gallery
    • 2020 MSBizAppsSummit Gallery
    • 2019 MSBizAppsSummit Gallery
    • Community Engagement
    • Community Calls Conversations
    • Experimental
    • Error Handling
    • Power Apps Experimental Features
    • Community Support
    • Community Accounts & Registration
    • Using the Community
    • Community Feedback
    cancel
    Turn on suggestions
    Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
    Showing results for 
    Search instead for 
    Did you mean: 
    • Power Apps Community
    • Galleries
    • Community App Samples
    • PowerApps Challenge Feb 2019

    PowerApps Challenge Feb 2019

    02-10-2019 17:45 PM

    gsivasai
    Advocate III
    1020 Views
    LinkedIn LinkedIn Facebook Facebook Twitter Twitter
    gsivasai
    gsivasai Advocate III
    Advocate III
    • Mark as New
    • Bookmark
    • Subscribe
    • Mute
    • Subscribe to RSS Feed
    • Permalink
    • Print
    • Report Inappropriate Content

    PowerApps Challenge Feb 2019

    ‎02-10-2019 05:45 PM

    Hi there!

     

    Had a lot of fun working on these challenges as quickly as I could. Below are my entries for the PowerApps Challenge:

     

    CHALLENGE 1

    For this challenge I could think of 3-4 possible ways to abstract the exact data source details from the user:

    1. SharePoint Permissions so that underlying lists/libraries are not known to the user
    2. Flow to fetch data from data sources so that data source info is completely abstracted
    3. Public APIs as data sources via Flow
    4. PowerApps PowerShell module to bypass/remove the consent popup prompting the user to allow data connections.

    For the reason of picking the shortest path from A-Z, I chose the first option of using SharePoint Permissions.

     

    SharePoint Configuration

    I chose two different SharePoint Lists as my data source. First list ‘Stores’ stores details of all stores in the area. This includes store number, name, city, state & zip.

    Stores ListStores List

     

    The second list stores ‘ServiceRequests’ for each store across a variety of products. This list has a lookup to the ‘Stores’ List.

     

    ServiceRequests.png

     

    For this challenge my test user has been explicitly given Read permissions to both Lists.

     

    permissions.PNG

     

    PowerApp Details

    The idea behind the app is to enable the user to pick a Store and view all Service Requests for that store. OnVisible of the app is a Concurrent call to fetch data from the two data sources added to the app. Concurrent() because performance is key to accomplish efficiency!

     

    concurrent.PNG

     

    The app consists of 2 galleries for each of the data sources. One gallery is set to display all stores from the collection. The other gallery is set to filter items from the Service Requests lists based on the store selected from the first gallery.

     

    gallery.PNGBoth data sources in actionBoth data sources in action

     

    Here’s the consent popup when the test user loads the app and the underlying two data source Lists are not visible to the user.

     

    Consent popupConsent popup

     

    CHALLENGE 2

     

    There are several ways to achieve this but for this challenge I chose to go the pure Flow route to keep it short and simple. And time is futile in this challenge 😊

     

    I have a SharePoint List (CandyInventory) for the inventory procurement maintenance with Title, SKU, Procured quantity, Sold quantity & In Stock Quantity.

     

    challengelist.PNG

     

    For this challenge I’m focusing on the shortest path to keep one informed on Out of Stock inventory.

    I have a recurring Flow that is set to run every day at 5 am. It is set to query the SharePoint List for all items with an OData Filter query of InStock <= 20 and sends an email notification with inventory details.

     

    InventoryTrackingFlow.PNG

     

    Below is one of the notifications I received.

     

    email.PNG

    For some reason it wouldn't let me  upload the solution packagae into the app gallery. So I included a screenshot of the solution in my tenant.

     

    FLow in a Solution PackageFLow in a Solution Package

     

    CHALLENGE 3

     

    For this challenge I used a button Flow where I can add an image, specify date, reason and upload the image to a SharePoint Document Library. The device location details are later derived from the Flow properties and the uploaded file metadata are updated.

    Here’s a snapshot of the flow I used. The file name needs to be extracted (highlighted below) from the trigger body since it’s not an OOB property available in button trigger properties.

     

    flowactions.PNGflowrun.PNGlib.PNG

    Preview file
    148 KB
    Labels:
    • Labels:
    • Data connections and mashups
    • Galleries and Forms
    • Security and access controls
    • Workflow and Process Automation
    Message 1 of 1
    1,020 Views
    0 Kudos
    Reply
    • All forum topics
    • Previous Topic
    • Next Topic

    Power Platform

    • Overview
    • Power BI
    • Power Apps
    • Power Pages
    • Power Automate
    • Power Virtual Agents

    Browse

    • Sample apps
    • Services

    Downloads

    • Windows
    • iOS
    • Android

    Learn

    • Documentation
    • Support
    • Community
    • Give feedback
    • Blog
    • Partners

    • © 2023 Microsoft
    • Follow Power Apps
    • Privacy & cookies
    • Manage cookies
    • Terms of use
    • Trademarks
    California Consumer Privacy Act (CCPA) Opt-Out Icon Your California Privacy Choices