Power Platform Community Forum Thread Details

Hello there.

I’m new to Power Apps and I’m trying to create a tool for entering monthly data by activity stage and job title for different types of projects. To do this, I made 2 galleries, one inside the other. However, when I run the app and try to move between the ‘TextInputs’ using the ‘TAB’ key, the field is selected and then deselected immediately after, requiring me to go through all the fields again.

Does anyone know why this happens and how to solve it?

If I just use de mouse, it works correctly, but the usability is not that good

For example:

Data input:

TAB key selected:

a few milliseconds later:

then I need to TAB twice to go to the second textinput in that row. If I'm trying to set the fifthy ou other ones, I need to press TAB many times as the column of the textinput

Categories:

Building Power Apps

Hi @ TR-31071115-0

The issue you’re experiencing with the ‘TAB’ key in Power Apps is a known one. When you use the ‘TAB’ key to move between fields in a gallery, the focus can sometimes jump back to the start of the row1. This happens because making a change to a field causes a Patch() OnChange. When you tab through the fields, the tab index jumps to the start1.

https://powerusers.microsoft.com/t5/Building-Power-Apps/PowerApps-Data-Entry-Grid-Tab-Key-Issues/td-p/618351

If that is the case try

Create a Collection: Create a collection that populates blank rows in your gallery to be written and saved each day1.
Set Items Property: Set the Items property of your gallery to this collection1.
Include Text Input Boxes: Inside your gallery, include text input boxes whose Default property is set to your desired fields1.
Write Changes to a New Collection: In the OnChange property of those input boxes, write changes to a new collection. This is what you’ll ultimately save back to your data source1.
Leave Original Collection Untouched: Your original collection remains untouched so that the gallery doesn’t get updated and reload1.
Save Changes: Once all changes are made, you can set the OnSelect property of a submit button to save the changes1.
This approach allows patches made to the new collection to be immediate and do not have any performance impact because you’re not writing back to the data source after each revision1.