Keyboard Shortcuts in Power Apps most Developer Don't know

Keyboard Shortcuts in Power Apps most Developer Don't know

Keyboard Shortcuts In Power Platform

Keyboard shortcuts for canvas apps

1. File

ShortcutAction
Ctrl+O (or Alt+F)Open a file
Ctrl+Shift+S (or Alt+P)Save the app with a different name
Ctrl+SSave the app with the same name or for the first time
Ctrl+Shift+PSave the app and activate the publish dialog
F12Download the app file (.msapp)
Alt+FOpen the File menu
File Shortcuts


2. Ribbon

NO.ShortcutAction
1Alt+Iselect the insert tab
2EnterRun the selected command
3TabMove between commands on the selected tab and then to the next tab


3. Editing 

NO.ShortcutAction
1Ctrl+ASelect all
2Ctrl+XCut
3Ctrl+CCopy
4Ctrl+VPaste
5Ctrl+ZUndo command
6Ctrl+YRedo command
7Ctrl+MAdd a screen
8Ctrl+= or Ctrl+Shift+=Zoom in
9Ctrl+- or Ctrl+Shift+-Zoom out
10Ctrl+0Fit canvas to page
11Shift+EnterBreak a line in a formula

4. Preview

NO.ShortcutAction
1F5Open Preview mode
2EscClose Preview mode, a dialog box, or a flyout pane

5. Canvas 

NO.ShortcutAction
1TabSelect the next control
2Ctrl+Click or Shift+ClickSelect multiple objects at once
3Right arrowNudge the selected control to the right
4Left arrowNudge the selected control to the left
5Up arrowNudge the selected control up
6Down arrowNudge the selected control down

6. Tree View

NO.ShortcutAction
1F2Rename a control
2EscCancel renaming a control
3Ctrl+GGroup/ungroup controls
4Ctrl+]Bring a control forward
5Ctrl+[Send a control backward
6Ctrl+Shift+]Bring to front
7Ctrl+Shift+[Send to back

7. Resize

NO.ShortcutAction
1Shift+Left arrowDecrease width
2Ctrl+Shift+Left arrowDecrease width slightly
3Shift+Down arrowDecrease height
4Ctrl+Shift+Down arrowDecrease height slightly
5Shift+Right arrowIncrease width
6Ctrl+Shift+Right arrowIncrease width slightly
7Shift+Up arrowIncrease height
8Ctrl+Shift+Up arrowIncrease height slightly

8. Text Format

NO.ShortcutAction
1Ctrl+BCycle through levels of bold
2Ctrl+ITurn italic on or off
3Ctrl+UAdd or remove underline

9. Alternet behavior

NO.ShortcutAction
1Alt or Ctrl+Shift1. Before selecting a control, hide design elements so that you can interact with the controls as the app's user would.
2. After initiating a resize or reposition of a control, holding down these keys overrides any snap points.

10. Other

NO.ShortcutAction
1F1Open documentation
2Ctrl+F6Navigate to the next landmark
3Ctrl+Shift+F6Navigate to the previous landmark
4Shift+F10Open a shortcut menu in, for example, Tree view

✨ Thanks for reading! ✨

I hope you found this blog on the Microsoft Power Platform helpful! From Power Apps, Power Automate (Cloud & Desktop), Canvas Apps, Model-driven Apps, Power BI, Power Pages, SharePoint, Dynamics 365 (D365), Azure, and more, I cover a wide range of topics to help you harness these powerful tools. Don’t miss out on future tips, tutorials, and insights—hit that subscribe button to get the latest posts right to your inbox. 💌

💬 I’d love to hear your thoughts! Drop a comment below with your questions, ideas, or feedback—let’s get the conversation started!

🔗 Let’s connect and grow together!
Follow me, Ravindra Jadhav, on your favorite platforms for even more content and updates on Microsoft Power Platform and related technologies:

  • 💼 LinkedIn – Let’s network and share ideas!
  • 💻 GitHub – Explore my projects and code.
  • 🐦 Twitter – Stay updated with quick tips and industry news.
  • 📺 YouTube – Watch tutorials and deep dives on Power Platform, Power Apps, Power Automate, and more!

Let’s build something amazing together with Power Platform and Azure! 🚀

Comments

Post a Comment

Popular posts from this blog

Display Dataverse Table Data In Power Pages by Using liquid Language

 Display Dataverse Table Data In Power Pages by Using liquid Language Display Dataverse Table Data In Power Pages by Using liquid Language CSS CODE:   /* styles.css */ /* Apply basic styles to the outer container */ .col-md-12.columnBlockLayout {     padding : 16px ;     margin : 60px 0 ;     min-height : 200px ;     background-color : #f5f5f5 ;     border : 1px solid #ddd ;     border-radius : 5px ; } /* Style the table */ .table {     width : 100% ;     border-collapse : collapse ;     background-color : #fff ; } /* Style the table header */ .table th {     background-color : #007bff ;     color : #fff ;     text-align : left ;     padding : 10px ; } /* Style the table rows */ .table td , .table th {     border : 1px solid #ddd ;     padding : 8px ; } /* Apply alternate row background color for better readability */...
Read more

Power Automate OData filter query in SharePoint Get Item

 Power Automate OData filter query in SharePoint Get Item In Power Automate, the OData filter query helps to retrieve only the data that matches specific criteria. Below is an example of how to write it in a flow. Example 1: Filtering SharePoint list items where Status is Approved Let’s assume you have a SharePoint list with a column called Status and you want to filter items where the Status is Approved . Filter Query: Status eq 'Approved' Status : The internal name of the SharePoint column. eq : OData operator for "equals." 'Approved' : The value you are filtering by. Example 2: Filtering records based on dates and another field Suppose you want to filter records where Status is Approved and the Created date is after 2023-01-01 . Filter Query: Status eq 'Approved' and Created gt '2023-01-01T00:00:00Z' and : Logical operator to combine multiple conditions. gt : OData operator for "greater than." '2023-01-01T00:00:00Z' ...
Read more

Understand Solution and Layers

Image
 Understand Solution and Layers In    In Solution, there are two distinct layer levels: Unmanaged layer . All imported unmanaged solutions and unmanaged customizations exist at this layer. The unmanaged layer is a single layer. Managed layers . All imported managed solutions and the system solution exist at this level. When multiple managed solutions are installed, the last one installed is above the managed solution installed previously. This means that the second solution installed can customize the one installed before it. When two managed solutions have conflicting definitions, the runtime behavior is either “Last one wins” or a merge logic is implemented. If you uninstall a managed solution, the managed solution below it takes effect. If you uninstall all managed solutions, the default behavior defined within the system solution is applied. At the base of the managed layers level is the system layer. The system layer contains the tables and components that are requir...
Read more