cancel
Showing results for 
Search instead for 
Did you mean: 
Drrickryp

The Ten Commandments of SharePoint in PowerApps.

I have been to the mountain and heard the words of the gurus.  I am referring to @RandyHayes , @WarrenBelz , @Shanescows,  @mdevaney and others too numerous to mention.  I now return with some wisdom for my fellow PowerApps sufferers who have been lost for 40 years in the SharePoint desert.  Here are my Ten Commandments (feel free to disagree)

The 10 commandments of SharePoint in PowerApps

  1. Thou shalt use only Single line of text, Numbers and Date/Time type columns.
  2. Thou shalt use a separate list instead of the Lookup column type and connect the lists between parent and child tables with the parentID as a number column in the child table.
  3. Thou shalt strive to use delegatable functions and operators in all formulas
  4. Thou shalt not use spaces or special characters in column names
  5. Thou shalt not use these reserved words for naming columns:
    • Name
    • Date
    • Day
    • Hour
    • Minute
    • Month
    • Selected
    • Value
    • Result
    • Color
    • Count
    • Download
    • First
    • Last
  1. Thou shalt not change column names once they are created or repurpose the holy Title field.
  2. Thou shalt use IntelliSense to find valid options and values in formulas.
  3. Thou shalt reset required fields to not required in SharePoint and use PowerApps to make them required.  If you cannot reset a required SharePoint field, give it a default value (this applies to the Title field in particular).
  4. Before building your PowerApp from scratch, go to your list in SharePoint and select the PowerApps dropdown and let PowerApps build your app for you.  It's a good starting point to build from. 
  5. Thou shalt consider using  a premium connector like SQL or Dataverse if your list will exceed 4000 items.

 

Your humble servant, @Drrickryp   

The Modern Prometheus    brain.gif

 

Comments

@Drrickryp 

e1ff60471a99dc34eedc050c48533f10.gif

@RandyHayes   That really cracked me up!!  I have tears in my eyes.  PERFECT!

@Drrickryp 

Another Mell Brooks favorite!!  

RandyHayes_0-1614902722589.jpeg

 

@RandyHayes 

I believe my jar was mislabeled.  It should have your name on it! 

@Drrickryp 

😂😂😂 Too funny....did you get Abby Something...

Heh, I won't mention any names but we know who they are!!

As long as you can do it all on a tablet

MosesTablet.jpg

@Drrickryp 
Amazing, this article made me laugh 😄

Just remember @mdevaney 

The early bird 🐦 gets the worm 🐍 but the second mouse gets the cheese. 🐁

Here is one I use:  Thou shalt not use the Yes/No column type. Thou shalt use the Choice column with Yes/No options instead. 

 

I know this goes against Commandment #1 but with the single select choice columns now delegable they aren't the pain they used to be.

@Jeff_Thorpe 

I like your amendment to the commandments sir!  I do this too because after the app is built someone always says: "we have yes and no... could you add a 3rd option?"  Then I have the flexibility to do so. 

@mdevaney , I do it because I can never get the Yes/No column to work as expected in a filtering condition. 

@Jeff_Thorpe  Maybe I'm missing something but what advantage is there for a choice column when you can use a single line of text and hard code your choices in PowerApps. Much simpler for filtering IMHO.  I absolutely agree with @RandyHayes about keeping things as simple as possible. Developers-vs-users.jpg

 

I particularly like this number 6 - Thou shalt not change column names once they are created or repurpose the holy Title field. And do we need to add - Thou shalt always start with small text and have to change it. 

I am using Yes/No and Multiple lines of text. It seems to breach first commandment. What is the reason we should avoid these two types of column?

Multiple lines of text are not an issue when you need them, but don't use them unless they are necessary as they have some restrictions compared to Single Lines.

Boolean (yes/no) were not Delegable in the past, but it seems they now are. I still do not use them, preferring a Text Yes/No for reasons mainly around the output in reports (we export to Excel a lot from SharePoint) - I have a very simple process allowing check boxes/toggles to be used.

Meet Our Blog Authors
  • PowerApps Community Mentor 2018, Practicing surgeon and former Professor of Surgery, University of Illinois, Chicago.
  • Jill of All Trades (Power Apps, SharePoint, PowerShell, Exchange, Power Automate and odds & ends of assorted other things)
  • I am the Owner/Principal Architect at Don't Pa..Panic Consulting. I've been working in the information technology industry for over 30 years, and have played key roles in several enterprise SharePoint architectural design review, Intranet deployment, application development, and migration projects. I've been a Microsoft Most Valuable Professional (MVP) 12 consecutive years and am also a Microsoft Certified SharePoint Masters (MCSM) since 2013.
  • I'm Tim Leung - a PowerApps builder. In addition to PowerApps, my main interests include building software with SQL Server and Microsoft .NET. I'm the author of 'Beginning PowerApps' - the first published book on PowerApps. You can buy this from Amazon and other leading bookstores.
  • Systems developer
  • My name is Timothy Shaw and I create digital solutions using the Power Platform, Office 365, and Azure SQL and handle the IT for a small company in the energy sector. When not building the future :), I enjoy playing guitar, good (or really bad!) sci-fi, Xbox therapy, and hanging with my wife and son. Twitter: @ShortForTim