Skip to main content

Low Code Solutions Require High Knowledge



Low code solutions such as Microsoft Flow and PowerApps offer faster development of some types of software solutions.  These products allow non-developers to create solutions or apps for functions such as approvals, routing or even integrating data for multiple systems.

Writing successful solutions, even without coding, requires quite a bit of knowledge and experience.  Here are some of the fundamental areas which are prerequisites:


  1. Understanding business processes. If you do not understand your business process, you cannot automate it.  This means a solid grasp of the data, the steps in the process, and how exceptions and errors are handled.  Normally this knowledge is in the domain of a business analyst.  
  2. Understanding data modeling. Most solutions involve some data storage, so you must understand field types, relationships, and concepts such as normalization to come up with an efficient data model. 
  3. Mastering the low code tool. You must thoroughly understand the product you are using to create the app.  It may have several similar features to accomplish the same task, and you must know enough to choose the right approach.  You can Google your way to learn the tool or go through a more structured training approach.  Microsoft offers extensive free training resources for its products. 
  4. Planning governance. You don't want to go from citizen developer who has the support of the IT department to a rogue shadow developer creating solutions which are not supported. Governance is the set of procedures to manage software solutions so that they are reliable, predicable and supportable. 
  5. Do no harm. You must follow IT practices to test your solutions before they go into production, develop in a non-production environment, document your steps and avoid breaking things.  These are second nature to software developers, but may be new concepts for the citizen developer. 
Developing low code software solutions requires no less discipline than custom software development.  Your IT department can provide vital support in order to make you low code solutions more successful.

For more information, see these related posts:

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises