The business problem
The store Barrio Demo counts stock on a loose sheet. Coffee appears available but only four packs remain; oil is out of stock and nobody has prepared replenishment. You will build a foundation for identifying each product, checking units, and finding the supplier.
The catalog contains eight references and 101 units. We will consider replenishment due for review when stock is less than or equal to the minimum. This is a case rule: being exactly at minimum must also appear in the alert.
1. Prepare the catalog
Download both CSVs. They use comma separators and decimal points in prices. If Excel opens them in one column, use Data → From Text/CSV, select comma and check data types before saving.
In Power Apps, select a practice environment. Create an unmanaged solution named Barrio Demo Inventario to group the components.
2. Create suppliers
Inside the solution, create the table Tienda Proveedores. Its primary text column will be named Proveedor. Add:
| Column | Type | Configuration |
|---|---|---|
| Codigo | Text | Required; examples P001 and P002 |
| EntregaDias | Whole number | Minimum 0 |
Enter the three CSV records through the data editor. EntregaDias is an operational reference for the case, not a delivery guarantee.
3. Create products
Create Tienda Productos and name SKU its primary column. Make it business-required. Add:
| Column | Type | Configuration |
|---|---|---|
| Producto | Text | Required |
| Existencias | Whole number | Minimum 0 |
| Minimo | Whole number | Minimum 0 |
| Precio | Decimal number | Two decimal places; represents EUR |
| Location | Text | Shelf or location |
In Relationships, create a many-to-one relationship to Tienda Proveedores, with the lookup Proveedor. Each product will be linked to one supplier in this practice.
A column with a display name does not itself guarantee uniqueness. In Schema → Keys, create Clave SKU on SKU. Save and check that the key finishes creating successfully before relying on it to prevent duplicates. If creation fails, check duplicate records and try again.
4. Load the eight items
From the table, use your environment's Excel/CSV import experience. Select the catalog and review mapping: SKU → SKU, Producto → Producto and other columns with the same name. Do not map SKU to the Dataverse GUID identifier.
If the experience requires a template, first export a sample record, retain necessary columns, and adapt the file. For eight rows you can also enter values manually.
When complete, review import errors and verify that eight products exist. Assign lookups to these suppliers:
| Proveedor | Articles |
|---|---|
| P001 · Distribuciones Centro | CAF-250, ARR-1KG, ACE-1L, PAS-500, GAL-200 |
| P002 · Bebidas Sierra | LEC-1L, AGU-15L |
| P003 · Higiene Norte | DET-2L |
Select existing records through the lookup. Typing a name in another column does not create the relationship.
5. Check the result
| Test | Expected result |
|---|---|
| Count products | Eight references |
| Sum Existencias | 101 units |
| Compare stock with the minimum | CAF-250, ACE-1L, LEC-1L, and GAL-200 need review |
| Review ACE-1L | Zero units; supplier P001 |
| Save Existencias = -1 | Rejected by the column constraint |
| Create another product with SKU CAF-250 | Rejected when the key is active |
If nine rows appear, check whether the duplicate attempt was saved before the key became active. Correct the duplicate and review the key; do not continue assuming uniqueness is valid.
Deliverables and next step
Keep the model to build the stocktaking app. Save a catalog screenshot and another showing the supplier relationship. The deliverable is the inventory foundation; sales and purchase movements would be added through further processes.
The conversation continues here
Questions and experiences
Stuck on a step or found another way? Share what you have tried and help those who come after you.
Read comments or sign in to participate.
Loading comments…
For a question about another topic, start a conversation in the community. Participation and privacy rules.