The purpose of this post is to highlight the table schema that I’ll be using henceforth, in my upcoming posts, targeting Microsoft PowerApps and Microsoft Flow. The table schema design is based on the Product Table from AdventureWorks. Here, I have highlighted all the fields used and their types. Some of the fields are custom so as to suit my case scenario.
|Make Flag||Choice||✔||0 = Product is purchased.
1 = Product is manufactured in-house.
|Finished Goods Flag||Choice||✔||0 = Product is not a salable item.
1 = Product is salable.
|Safety Stock Level||Number||✔||Minimum inventory quantity|
|Reorder Point||Number||✔||Inventory level that triggers a purchase order or work order|
|Standard Cost||Currency||✔||Standard cost of the product|
|List Price||Currency||✔||Selling price|
|Days To Manufacture||Number||✔||Number of days required to manufacture the product|
|Product Line||Managed Metadata||R = Road
M = Mountain
T = Touring
S = Standard
|Class||Managed Metadata||H = High
M = Medium
L = Low
|Style||Managed Metadata||W = Women’s
M = Men’s
U = Universal
|Sell Start Date||Date and Time||✔||Date the product was available for sale|
|Sell End Date||Date and Time||Date the product was no longer available for sale|
|Discontinued Date||Date and Time||Date the product was discontinued|
|Product Image||Hyperlink or Picture||Image of the Product|
|Modified||Date and Time||SharePoint default|
|Created||Date and Time||SharePoint default|
|Created By||Person or Group||SharePoint default|
|Modified By||Person or Group||SharePoint default|
- Since, this table will be used a lot in my future posts, instead of defining it again and again, I’ll be using this post for reference.