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!
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 preceding 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.
Description This blog shows you how to work with the CDS Entity Option Set fields for the PowerApps Patch and the Flow Condition to work successfully.
Scenario Consider a ticketing PowerApp which is using a CDS entity. The status of the ticket is saved in an Option Set field in the entity. When the ticket is created the status is changed to In-Progress using the patch function and when the ticket is completed an email notification is sent using Flow.
"What hump?"It is amazing that you can actually create a App with PowerApps without understanding the principles of relational database design. What is not amazing is how inefficiently the app will function with respect to creating new records, retrieving accurate and usable information, updating existing records that need to be changed, and deleting the right records without removing other valuable information from the database.
Working on PowerApps with big data set is subject to "Delegation", a PowerApps feature made to ensure good performances into apps. This is a key concept as it will define which data source you are able to use to achieve what the business scenario requires. This post provides detailed explanations about the delegation concept.
This blog describes how you can save multiple comments to an single data entry using one-to-many relationships. The blogs walks through how you use IDs from the tables to build the relationships. The demo includes a sample app used by a school teacher to save comments and scores of students, however, the same app can be used for other similar scenarios. Majority of the content is covered in the video, however, expressions and important links are provided here.
This blog post is part of a series called AMFTF (a message from the field) containing short blog posts about a best practice, a functionality, a how-to and/or something just worth writing a blog post about Todays topic is about investigating if changing the setting "Data row limit for non-delegable queries" can improve performance for delegable queries.
Can I use a SharePoint list as a data store in my PowerApps? In case I will have more than 10 000 items? Or Should I use SQL Database instead? Are there any shortcomings with these options? How about Common Data Service for Apps?
I wrote this article with these questions on my mind.
This blog post is part of a series called AMFTF (a message from the field) containing short blog posts about a best practice, a functionality, a how-to and/or something just worth writing a blog post about Todays topic is about a community initiative called 'PnP PowerShell'.
This blog post is part of a series called AMFTF (a message from the field) containing short blog posts about a best practice, a functionality, a how-to and/or something just worth writing a blog post about Todays topic is about indexing SharePoint lists.
This blog post is part of a series called AMFTF (a message from the field) containing short blog posts about a best practice, a functionality, a how-to and/or something just worth writing a blog post about Todays topic is about showing all SharePoint Online list items in a gallery.
The Microsoft Business Applications Summit is almost here, and even if you’re not joining us in Seattle, you can take part too – catch the opening keynote livestream on Monday, July 23 from 8:30 – 10am PDT, and learn what’s new and next for Microsoft Business Applications.
Working with barcodes and QR codes has improved all kinds of business processes for decades now. As can be read from comments in the PowerApps community, many people expect PowerApps to support working with them.
This blog post is about the current state of working with barcode/QR code images in PowerApps. And yes, working with QR code images has arrived
It is recommended to update or (re)publish your app every six month. Click here to go to the related webpage. To be honest, I do not know if this it true for SharePoint forms (I assume it is), but for apps it is recommended.
So how does one know which apps are not updated or (re)published in six months? Well, PowerShell to the rescue!