Blog Post

Educator Developer Blog
2 MIN READ

Build a Mobile Sales Application with Power Apps

RachelIrabor's avatar
RachelIrabor
Iron Contributor
Apr 20, 2023

This is part of the Let's Build Together: LowCode Edition show where you learn how you can use applications and services in Power Platform to accelerate digital transformation of business processes.

 

This show is designed to walk you through how to build End to End solutions using Microsoft Power Apps, automate their processes with Microsoft Power Automate in a span of just 2 weeks. Power Platform skills will open doors for you in your career

 

Use Case Project – Mobile Sales Application

 

Watch Live Practical Guide on-demand

Solution Considerations before development

Before you build an application, you should have some thought and break down what you want to do before building. This process is often called "Solution Architecting". While we will not be taking a lot of time doing this, I would like to introduce you to the basics of it.

 

In our session case we will look at:

The Front-end built with Powerapps, you can learn more on How to build a canvas app 
The Middleware that allows us to run the background process of our Asset Manager solution. This can be configured by using Approval flows within Power Automate 
The Back-end allows us to store all the data from our solution and to achieve this we will Set up tables in Microsoft Dataverse

 

Business Rules

  1. The sales representative captures sales details from customer. Upon making a sale, the representative selects the customer’s requested product from a list of products and proceeds to capture the Customer Name and Emailto send/generate an invoice for the customer.
  2. On App start, the details of the signed in Sales Representative are captured and store locally.
    1. OnStart property - Set(varSalesRep, User())
    2. On the gallery/list of products, the sales rep presses a button to generate an invoice for the customer.
    3. OnSelect property of Button – Set(varSelectedProd, ThisItem)
  3. On the edit screen, the sales rep only captures the Customer Email and Name
    1. Default property for Sales Rep Name – varSalesRep.FullName
    2. Default property for Sales Rep Email – varSalesRep.Email
    3. Visible property for Sales Rep Name – False
    4. Visible property for Sales Rep Email – False
    5.  Default Property for Product Name – varSelectedProd.’Product Name’
    6. Default Property for Product Cost – varSelectedProd.’Product Cost’
    7. DisplayMode property for Product Name – DisplayMode.Disabled
    8. DisplayMode property for Product Cost – DisplayMode.Disabled
  4. The sales rep enters the sales number in the format of #ddmmyy-number(incremented by 1) (e.g #270223-01).
  5. The sale status is updated automatically by a Power Automated flow
    1. Visible property – false

Feedback

We want to hear from you based on your learning experience through the series. Your feedback will help us to improve your experience with the Power Platform Products. Click here to drop your feedback

 

 

Updated Apr 17, 2023
Version 1.0

2 Comments

  • getservicex's avatar
    getservicex
    Copper Contributor

    Great walkthrough! For developers building mobile sales apps, it's helpful to understand how user behavior shifts based on local pricing expectations and device affordability.

    In some markets, especially in South Asia and the Middle East, mobile app users often compare phone models based on https://pricesupdates.com before making purchase decisions. These behaviors are important to consider when designing UX flows or pricing logic within Power Apps.

    Appreciate the detailed breakdown in this post — especially the use of Dataverse for back-end logic.

  • If you're looking to build a top-quality education app, contact Hyena Information Technologies. They deliver 100% reliable, high-performance mobile apps tailored to your needs.