This is a continuation of the Business Card Scanner using Microsoft PowerApps vBlog I had recorded back in August, 2018. This blog walks you through step-by-step to build the key features you need. Majority of the explanation is done in the video, this blog provides formulas and links to helpful articles.
This immersive event offers 90-minute, multi-level sessions on Power BI, PowerApps, and Microsoft Flow. All sessions are deep-dives, presented by technical and functional experts, MVPs, and Microsoft team members.
Not to long ago, Microsoft introduced the column type “Location” in SharePoint Online. This is a great addition for business solutions. From a PowerApps perspective, the usefulness is limited to showing data (Country/Region, State, City, Postal Code and Street).
So is it not possible at all to update a location field from PowerApps?
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 making your apps a bit more perfect when switching screens. The function "Set" is used for this.
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 one of my best tips related to SharePoint forms.
This blogs focuses on how to add defaults to a SharePoint Customized (or PowerApps) form. The list in this demo includes all the column types including managed metadata. The video walks you through the steps in detail, however, this blog contains all the functions incase you want to copy and paste
This is the 5th in a series of blog posts regarding database design principles and PowerApps. It presupposes that the prospective designer has reviewed the first 4 posts in the series and now has constructed the tables and defined the relationships between them. All data points are reduced to their smallest logical component and each table has a single characteristic with fields that are either a number, currency, text, Boolean, hyperlink, or date/time and are not calculated from other fields. Each cell of the table contains a single value or fact. Each table has a primary key and there are no duplications of data between the rows. All tables are connected by Primary and Foreign keys. All Many-to-many relationships have been changed to two One-to-many relationships with a Junction table between them.
A very handy way to assist your Users in filling out forms is to autofill labels and TextInput fields for the City and State based on the user entering the Zip Code and then using the Lookup() function to pull in the City and State from a Lookup table. This eliminates spelling errors and saves clerical personnel time as well since they only need to enter the Zip Code for any address. The technique involves bringing in the City, State and Zip Code data with the Excel Static Data connector. This method also avoids delegation issues since Static Data is not affected by them. A collection of >42,000 items can be created in seconds. You're putting me on!
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 using a "Single line of text" column type instead of a "Lookup" column type in SharePoint Online.
This blog focuses on the on offline capability of PowerApps. Here you'll see the key features you need to add to your PowerApp in order to take input when there is no internet connection available and automatically upload it to your data connection. This written blog explains the features and the formulas/expressions used. The video deep-dives in the entire process. A copy of this app is attached to this blog.
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.