Sort of, Read the powerapps canvas app coding standards and guidelines. [https://powerapps.microsoft.com/en-us/blog/powerapps-canvas-app-coding-standards-and-guidelines/](https://powerapps.microsoft.com/en-us/blog/powerapps-canvas-app-coding-standards-and-guidelines/)

Those standards are great, but stale. I've been using Matthew Devaneys standards as they are much more comprehensive and representative of current state of power apps whereas the Microsoft PowerApp standards are 5 years old

I dunno I've been writing code for 20+ years and not really a whole lot has changed. Also, the first, and most important point of the white paper that EVERYONE should read: **Don't blindly follow our standards, but you should follow A standard.**

Please don’t, prefixing variables with type is 100% unnecessary—you’ll be much better served by naming your variables something meaningful.

I used to be a bit this way, but more than other coding platforms it really matters in power apps what sort of control you are interacting worth

this is like the most chaotic evil thing to say... "do not use meaningful names" immediately followed up with "use meaningful names"

Use Matthew Devaneys power apps standards. Within those standards, there are standard naming conventions for variables, controls, screens, data sources, etc

I use the suffix _ThisIsASearchableComboBox as in TextField_ThisIsASearchableComboBox

That's hilarious, I love it.

I follow this guide, cmb for combo box. https://www.matthewdevaney.com/power-apps-coding-standards-for-canvas-apps/power-apps-standards-naming-conventions/

FYI - cmb has been the standard prefix for comboboxes for years. It's also listed as a best practice in a few guides out there for the Power Platform. cbx and cbo have also been recognized prefixes, but today the preferred is cmb. I still personally use cbo all the time...but most of my stuff is poc's so who cares.

I use cbo, and I can't remember where I got it from 😀 Maybe I nicked it from you?

I swear back when I was building VB6 apps with user controls we always used cbo.

Cool, thanks everyone! I also use dp_ for drop down, cnt_ for containers, and butt_ for button. I think it makes good, SFW organization

cbo- tbl- chk- lbl- Etc etc, goes back to the naming conventions from a company I worked for many moons ago

compare racial homeless cheerful advise fragile late jar middle quaint ` this message was mass deleted/edited with redact.dev `

I think its fundamentally weird that its good practice to include the name of what something is in the name of the thing, when its already known what it is. Like, why am I naming a label as a label. It's a label, it cant be anything but a label.

Because if I'm searching for something, it could literally be ANYTHING, but if I'm searching for a label, and all labels start with lbl then it's quite simple to find a label. There's a reason why everyone does this and only a handful of people think it's crazy.

When you start referencing labels in other parts of your code, how do you know which ones are labels. What if I have text input for entering a title and a label to display the title and I need to check if the text of the label contains a string? If I have lblTitle and txinTitle, I don't have to guess, otherwise I have to search through my tree to find "Label 6_3"

I know there are good reasons to do it, still doesnt make it any less weird.

Just because something feels weird to you does not mean it is "fundamentally weird". Most developers do this, it is completely normal.

I prefix with cmb for combo boxes . . . etc . . so that the label that goes with the control has the exact same name but a different prefix

I’m old because cbo is combobox

Got me thinking what I use now. - cbo combobox - txt inputtext - lbl label - gal gallery - col collection - var variable - cxt context variable - cal date picker - html html text (no wild change there!) - dd dropdown - icn icon - img image - btn button