The blog post by Timo Pertilä is an insightful discussion about some common patterns seen in first and second Power Apps made by developers. These are tips and tricks one learns from examining others' work, often revealing new methods, and strategies of accomplishing tasks better in Power Apps.
The author talks about the misuse of LookUp
commands, where developers often unnecessarily repeat the LookUp function giving redundancy in the code.
Next, he discusses the redundant use of variables to check whether a line on the form is being viewed, edited or created. The form status can be directly checked from the form itself.
The article then moves on to the topic of variables in Power Apps, highlighting the differences and use-cases of global and local variables. Global variables, while easy to use, are performance-heavy and should be used only when necessary.
You shouldn't group controls due to the problems that it can cause when trying to modify them. Instead, Pertilä recommends using containers for easier management.
Another discussed issue is the repetition of control, especially in navigation. Navigation is best implemented as a gallery, and if used on several screens, should be implemented as a component.
The author then talks about redundancies in code due to duplications in multiple places without a significant reason.
Lastly, the blog post discussed the issues with dependencies between screens, which can complicate optimization and potentially causing unusual situations.
Understanding the potential pitfalls and inefficient design choices is crucial in creating high-quality Power Apps. Efficient use of LookUp commands, smart management of variables, effective usage of groups and containers, reducing repetition of controls and unnecessary code, and cautious management of dependencies between screens are the key areas to focus on. More efficient, maintainable and elegant solutions lie in the adoption of recommended practices, contributing to a better user experience and performance of the apps.
The blog reviews the usage of Power Apps, focusing on the frequent implementation mistakes identified in many beginner's first and second Power Apps. These common errors are not due to stupidity but inefficiency, which could be rectified to make Power Apps usage more effective and elegant.
One such inefficiency highlighted is the unnecessary use of LookUp commands. Developers often use the LookUp function to fetch already available customer data, which is inefficient and quite redundant. Instead of using a formula such as LookUp(Accounts, 'Account Name' = galAccounts.Selected.'Account Name').'Account Number', the author recommends using simpler references like galAccounts.Selected.'Account Number'.
To learn more about this topic, readers are advised to explore more Power Apps exercises and practice projects to fully understand common mistakes and the most efficient solutions.
Microsoft specialist, Microsoft certified professional, Microsoft certified expert, Microsoft solutions expert, Microsoft technology expert