Connect with experts, collaborate with your community and maximize learning opportunities at Microsoft Business Applications Summit. Back for its second year, this is the premier place for power users, analysts and technical architects to get hands-on with the tools you use every day – and get a sneak peek at what’s new and next. Registration is open – don't miss it! Read more...

This blog pIt could work!!ost is the fourth of a series and it builds on the concepts and terms discussed in the preceding three posts.  At this point the designer has acquired all of the necessary data points and organized them into tables, each of which defines a single characteristic.  At this stage, it is important to add a Primary Key to each table and then link the tables together using these keys.  There are three possible relationships between the tables.  One to one, One to many and Many to Many.  This post will demonstrate how to connect the tables using the keys and how to deal with each type of relationship in the PowerApps setting.  

This post is the third in a series following the steps in designing the database that will provide the Back-end of a PowerApp.  The terminology assumes that you have reviewed the pr

eceding two posts.  Hopefully, following this review, the prospective designer will be ready to take all of the data necessary for the application, break each datapoint down to its smallest usable components and then construct the tables.  The designer will then examine each table to eliminate redundency. This process is called Normalization.  A sample table will be provided and the first 5 forum members to successfully normalize the the table will be given double kudos.  

“Start with the customer and work backwards” – Jeff Bezos

“If you don’t know where you are going, it’s unlikely that you will get there except purely by accident, involving innumerable trials and errors” – Me