Skip to main content
Community site session details

Community site session details

Session Id : iJNkZU0EnlEVXOeAyNUF1c
Power Apps - Building Power Apps
Answered

Best way to approach Invoice Processing app

Like (0) ShareShare
ReportReport
Posted on 23 Oct 2023 20:37:55 by

Hello!

 

I am building an app to allow a client to process invoices digitally.

 

They need to be able to attach a copy of the invoice, enter in all details about the invoice (date, due date, supplier number, approvers, supplier name, etc.). In my mind, I envisioned data such as supplier number, name, etc. being stored in a SP list and then fed into the app via an edit form for easy selection.

 

However, this is where I need help ... each invoice may need to be assigned to several Expense Code #s. Note, it may not always be an equal amount charged amongst those Code #s (an invoice for $250: one Code may pay for $45, another may pay $205). Then, once the Code #s are identified (to include how much they will each pay toward the overall invoice amount), as a control, the user would like to see on screen the breakout of charges and how they equal up to the original invoice amount.

 

Appreciate any guidance!

 

 

  • Verified answer
    mpistil Profile Picture
    on 25 Jan 2024 at 20:22:24
    Re: Best way to approach Invoice Processing app

    Thanks, @jcfDaniel for the tip! I am not familiar with Relational Databases, so I am going to add that to my list of things to investigate.

     

    My company has not yet transitioned to Dataverse; we are using SharePoint for storing our data. What I ended up doing was for the Parent record -- which was collected via form -- , upon clicking of the "Submit" button, I did a ClearCollect of the data (collection name, "lastitem") and then did Patch/Defaults to write to SharePoint. The Submit button would then navigate you to the page for the Child data.

     

    Then for the child record -- collected via form -- I had a data card for Parent ID. I hid the data card visibility wise, and for the default control did "First(lastitem.ID)". It has been working like a charm.

     

    I suspect though that if I had more than one user in the app, which I won't, I would have to probably consider what would happen if two people were entering data at the very same time.

  • jorge.daniel Profile Picture
    1,430 Super User 2024 Season 1 on 24 Oct 2023 at 07:56:35
    Re: Best way to approach Invoice Processing app

    Hi,

     

    Are you familiar with relational databases? 

     

    You need to create 2 tables: Invoice and Invoice Detail and connect them through an ID on the Invoice table. On the detail table you assign expense codes by lines.

     

    Also, consider expense codes and a supplier tables.

     

    That´s great stuff for dataverse 😉

     

    Regards

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing our 2025 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for…

Paul Stork – Community Spotlight

We are honored to recognize Paul Stork as our July 2025 Community…

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 637 Most Valuable Professional

#2
stampcoin Profile Picture

stampcoin 570 Super User 2025 Season 2

#3
Power Apps 1919 Profile Picture

Power Apps 1919 473

Loading complete