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!
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.
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
WarrenBelz
637
Most Valuable Professional
stampcoin
570
Super User 2025 Season 2
Power Apps 1919
473