cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Mike2500
Level 8

Apps should have fewer than 60 fields?

According to the performance tips from Microsoft: "Don’t add more than 500 controls to the same app". While this seems reasonable, if you use the wizard to create an app you get three screens: edit, display, and gallery. Both the edit and display screens use forms, which have cards, which in turn have multiple controls. Simple math shows that the soft limit of 500 controls will be exceeded with only 60 fields. 

 

Am I missing something about these recommendations or about what constitutes a control? This seems extremely limiting, and clients with InfoPath forms with 100 fields won't appreciate hearing this guidance. Any thoughts or suggestions? 

6 REPLIES 6
Super User
Super User

Re: Apps should have fewer than 60 fields?

@Mike2500 

I believe ManCat is already answering your topic in the original thread  https://powerusers.microsoft.com/t5/Building-Power-Apps-Formerly/1-PowerApp-with-60-to-70-screen-Vs-...

 

If you feel this is a duplicate topic please close the thread.

Mike2500
Level 8

Re: Apps should have fewer than 60 fields?

I posted separately, as officially I was being off-topic there. This is an important issue for the folks who need to migrate off of InfoPath, as apparently there are quite a few InfoPath forms out there that will violate the Microsoft stated best practices if they are re-built in Power Apps. If I'm wrong about this, I'd love to hear what I got wrong. 

Super User
Super User

Re: Apps should have fewer than 60 fields?

@Mike2500 

Understood.

 

Before I leave the thread just wanted to share a link to a talk that was at MS Ignite this year in case you find it helpful.  I didn't get to attend this talk due to scheduling conflicts but I had it on my list to see.

 

Modernizing InfoPath Forms with PowerApps

Learn tips on how to find, triage and modernize InfoPath forms with Microsoft Power Apps and SharePoint. See what critical business processes look like when they take advantage of the full capabilities of SharePoint and the Microsoft Power Platform. See what's in the roadmap for upcoming features.  https://myignite.techcommunity.microsoft.com/sessions/86274?source=sessions

Mike2500
Level 8

Re: Apps should have fewer than 60 fields?

I saw that one already. Unfortunately, the session did not cover realistic forms or scenarios. The demo forms only had 4 or 5 fields, like the majority of the examples in the documentation.

Super User
Super User

Re: Apps should have fewer than 60 fields?

Fair enough.  Only so much that can be accomplished in a 45 session to a general audience I suppose.  Overall though I gotta say the MS Ignite was a pretty excellent experience.

Highlighted

Re: Apps should have fewer than 60 fields?

For starters there is seldom a justifiable reason to have multiple Form controls for either displaying a specific item, or editing an existing item or adding a new item for that matter to a specific list.

All that functionality can easily be incorporated into just one single mode. Thereafter you can simply set the FormMode when you navigate to that screen using a variable indicating what the FormMode should be by passing it, along the selected item record from the gallery control if you want to display or edit a specific item in the list.

Even if you navigate to that screen setting the FormMode to Display, you can equally simply add an Edit button to the screen displaying the form, which again just sets the.value of the variable. For the FormMode property on the form, set the value to the name you’ve assigned to variable.

There may subtle difference you may need to make on same of the Data Cards in the Form, but making those generally minor changes is a lot less effort then managing 2 different Forms on different screens in your app, especially when it comes to trying to keep both forms rendering the form fields similarly from a UX perspective.

Whatever session anyone may have attended at the MS Ignite conference recently as it relates to previous comments on this thread, sounds to me like it was a complete waste of time.

Firstly I have created a Form before on a screen in an app that contained in the region of 50 Data Cards, each with 3-4 screens. So that screen alone had in the region of 200 controls on it. If i recall there were perhaps around 10 screens in that app, and multiple SharePoint Data Source connections, a number of which contained more the 2000+ rows.

That said, I am not big fan of talking about theoretical best practices from a performance specific insofar as PowerApps is concerned, however I do by and large agree with the guidance published by Microsoft pertaining to recommendations and even I’d go as far it is surprisingly good (compared to some of the other document published by Microsoft on mostly other products).
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/performance-tips

However I would say that you are by all accounts reading a little too much into reverse calculating that the recommended soft limit of 500 controls can possibly be suggestive of that potentially implying that could possibly translate to your app potentially being constraining to about 60 “fields”, at which time you could potentially run some performance issues. You won’t. I am a big advocate of reusing the same controls you may have on any given screen, when in scenarios where those exact same controls can potentially be used for entirely different purpose, depending on what functionality the user may possibly want to do on any given screen at any given time.

To give you an idea of just much functionality can in fact be exposed in some apps I have recently created and recorded a number of demo video of those apps uploaded to YouTube, pick any or all of them if you interested, and see for yourself what functionality is showcased in each of the videos of the demo apps I created. Then consider that not even a single one of the apps demonstrated in any of these videos contain anything more than a screen in each of those apps, and how much functionality is nonetheless showcased in each demo video...
https://youtu.be/vSbwmHfqK3c
https://youtu.be/poKsDNYm9Jw
Blog: https://masteroffice365.com/powerapps/

https://youtu.be/lL2UaetkpXQ - GPS
https://youtu.be/DCdvwTE7LIw - Search

Helpful resources

Announcements
thirdimage

Power Apps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Power Platform World Tour

Find out where you can attend!

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

SecondImage

Difinity Conference

The largest Power BI, Power Platform, and Data conference in New Zealand

Top Kudoed Authors (Last 30 Days)
Users online (4,097)