Dataverse design for an Inventory PowerApp

(0) Share

Report

Posted on by MaFe

Hello

I'm tasked with creating a power app that will be used to keep inventory of parts, tools and euipment on a hotel ship.

The idea is to create a list of items with meta data and quantity for different department (hotel, nautical, maintenance, gastro)

Then couple of times every year, employees will receive a task to check each item and quantity and log current state.

In the end the approved outcome of this task will be used to update inventory status for every item.

I'm new to PowerApps and Dataverse & I'm looking for help to review my tables design.

Do I need to add CreatedAt/UpdatedAt/UpdatedBy data to tables or is this automaticaly done in Dataverse ?
Am I missing anything that might bite me later ?
Do you have any suggestions how to adjust my design ?

Thanks

Marek

Categories:

Microsoft Dataverse with Power Apps

database.png

I have the same question (0)

All responses (2)

Answers (0)

MarioRing 541 Super User 2024 Season 1 on at

Like (1)

Report

Hi,
I love your design! I am personally into old-school software design - today in no-code/low-code universe people usually forget to create and validate the design before they start actual customization. Excellent job! You can also draw use cases and sketch the forms/screens of the user interface.

Do you want to use Model Driven App or Canvas one?

There are some additional concepts that you should check - how security roles work, and when choose "Option Set" instead of lookup to another table.

On the other hand, if it's a new area to you, you can improvise and start building your solution directly in the app to verify your ideas.

By default, all Dataverse tables have "Created on/by" and "Modified on/by" columns, and they are automatically populated by the system.

Inventory management is an extremely popular type of application, you can analyze some template solutions provided by Microsoft to get more ideas. Go to https://make.powerapps.com, click "+Create" button and choose "Asset Checkout" or "Inventory Management" templates. You can also find many insightful video tutorials on YouTube.

Focus on user experience - try to make the app as much accessible and convenient to use as you can.

Was this reply helpful? Yes No
Drew Poggemann 9,287 Most Valuable Professional on at

Like (2)

Report
Hi @MaFe ,

Thoughts on your data model (after initial review)

First of all, the createdon, modifiedon, created by, modified by fields all exist on the dataverse. You will not need to create these.

The Owner field on the tables is out of the box as well so where you have "UserID", this would be exist already and allow you to assign records to users or teams.

Status Table - normally you would utilize the Status and Status Reason fields on the tables and not have a separate table for this.

As I think about the Location, Storage Room, Stock Status tables

Inventory - This table could have the fields like the Item (FK), Location Type, Quantity, Disposition, Location. This would be the current inventory position for each item at a location.

Location - This table would be the locations of the inventory. Should have things like Name, GPS, Address, etc. You might want to look at this having a parentID as well on this table to the same table to be able to have hierarchies of locations.

I didn't see any transaction table for inventory in / out. If you needed this it would also add some complexity to the structure

I see you have a relationship from Inventory Task to Item where it looks backwards. You should have a 1:N from the Item to the Inventory Task vs. the opposite.

I would not create an Item Meta table but utilize the Item table for this information.

Was this reply helpful? Yes No