The new update broke my apps with triggering the OnSelect property once it has been pressed once. Example: I have a screen with a modern table control. OnSelect stores the item in a variable "varSelectedItem" and then navigates to another screen where the corresponding Form for that variable is displayed. Pressing a button which calls the Back() function, navigates back to the previous screen where the modern table control was but the OnSelect property is triggered automatically as soon as the screen becomes visible, returning to the form once again. Had to restore to previous version temporarily until I find a workaround. Multiselect is probably the single most important update which opens a new world of posibilities. Once the filter button becomes available, there will be less need to even have a filter dropdown anymore. Keep up the great content!
@@svenmeyer2901 Glad you liked the video! Here’s a fix for your issue with the OnSelect property. I’ve been using this for a couple months since I’ve always had problems with it re-selecting when the screen loads. 1. In your OnSelect property, add this to the end of your current formula: UpdateContext({ctxTableFix: true});UpdateContext({ctxTableFix: false}) 2. In your table’s Items property, add this as one of your Filter function arguments: ctxTableFix = true || ctxTableFix = false || IsBlank(ctxTableFix) Doing these two things will create a context variable called ctxTableFix, and adding this to your filter will basically cause the table to force an update whenever you select a record (because ctxTableFix will change from either blank to true or false to true, then right back to false). Forcing that update will deselect the current record (which you won’t have seen since you’ve navigated away), and when you return back to the screen it should no longer have a record selected. Let me know if that works for you!
Hey there! You’ll need the format of the column in your data source to be currency. In this case it is a column in Dataverse set as currency. Keep in mind you introduce complexity using the currency column type, so I would almost recommend against utilizing it unless you have a specific use case.
Hello! There’s no select all option on the table yet when viewed in the desktop version. You can select one item, hold shift on your keyboard, then select another row lower in the table to select all the rows in between. With that in mind you can select the first row in the table, hold shift on your keyboard, then select the last row of the table to select all the rows at once. Hope that helps!
I see you have a searchbox in this example. I'm experiencing some strange unexpected behaviour when I use a searchbox. On first load the items in the table dynamically filter out when I type a character (or multiple characters) using the "Trigger output - Keypress" on the input field. So far so good, however. Once 1 select 1 row in the table the focus of the searchfield gets "lost". Now i have to manually put the focus on the searchbox for every character i type. Do you happen to experience the same thing?
Hey there, I unfortunately experience the same issue. This is being caused by a cell in the table being selected (which you can tell once you click on a row that the cell has a black border). There isn't currently a way to clear this while staying on the same screen. The only way I have found to fix this is to have something in your OnSelect property of the table that takes you away from the current screen. Think of something like selecting a row taking you to another screen to edit that row on a form. When you return back to your screen with the table, the cell should be unselected. This also has a side effect of triggering the OnSelect of the table when you navigate back to the table screen, so you'll need to add two lines of code to your table: 1. In your OnSelect property, add "UpdateContext({ctxTableFix: true}); UpdateContext({ctxTableFix: false})". This creates a context variable and sets it to true, then immediately sets it to false. You can put this after whatever action you take in your OnSelect property, so if you're navigating to a different screen you could put this after your navigate function. 2. In the Items property of your table, assuming you're using a filter function on a data source, you'll want to add the following as one of your filter function arguments: "ctxTableFix = true || ctxTableFix = false || IsBlank(ctxTableFix)" This will cause the table control to refresh itself when ctxTableFix changes in value, so basically it will unselect the row that you clicked on since it sees the value changing to true then back to false. This will stop the OnSelect function of the table from being triggered when you navigate back to the screen containing your table. I know that's a lot of hoops to jump through but I hope that helps!
@PowerAppsGuy not as crazy as ChatGPT though. It's workarounds for similar problems are using timers, it proposed timers for double click action on a row as well 😅 But thanks for looking into it. I'll try and describe the problem as well as I can to MS support. Same functionality in combination with the classic table does work as you'd expect it to.
![LAVROV's interview with Tucker CARLSON 😁 [Parody]](http://i.ytimg.com/vi/mbMemqc-QEk/mqdefault.jpg)
Short and to the point, I like it.
The new update broke my apps with triggering the OnSelect property once it has been pressed once.
Example: I have a screen with a modern table control. OnSelect stores the item in a variable "varSelectedItem" and then navigates to another screen where the corresponding Form for that variable is displayed. Pressing a button which calls the Back() function, navigates back to the previous screen where the modern table control was but the OnSelect property is triggered automatically as soon as the screen becomes visible, returning to the form once again.
Had to restore to previous version temporarily until I find a workaround.
Multiselect is probably the single most important update which opens a new world of posibilities. Once the filter button becomes available, there will be less need to even have a filter dropdown anymore.
Keep up the great content!
@@svenmeyer2901 Glad you liked the video! Here’s a fix for your issue with the OnSelect property. I’ve been using this for a couple months since I’ve always had problems with it re-selecting when the screen loads.
1. In your OnSelect property, add this to the end of your current formula:
UpdateContext({ctxTableFix: true});UpdateContext({ctxTableFix: false})
2. In your table’s Items property, add this as one of your Filter function arguments:
ctxTableFix = true || ctxTableFix = false || IsBlank(ctxTableFix)
Doing these two things will create a context variable called ctxTableFix, and adding this to your filter will basically cause the table to force an update whenever you select a record (because ctxTableFix will change from either blank to true or false to true, then right back to false). Forcing that update will deselect the current record (which you won’t have seen since you’ve navigated away), and when you return back to the screen it should no longer have a record selected.
Let me know if that works for you!
Great video thanks for sharing this
Glad you enjoyed it!
Apparently currency columns are not working. It displays correctly in studio but not in live page.
There are many bugs still with the modern controls but they are fixing more and more every week. Hope you enjoyed the video!
How do you format the money column like this? I've tried countless times but to no avail. Thanks for the video!
Hey there! You’ll need the format of the column in your data source to be currency. In this case it is a column in Dataverse set as currency.
Keep in mind you introduce complexity using the currency column type, so I would almost recommend against utilizing it unless you have a specific use case.
How to use select all rows in the table in web version? I see this option available only for the mobile view.
Hello! There’s no select all option on the table yet when viewed in the desktop version. You can select one item, hold shift on your keyboard, then select another row lower in the table to select all the rows in between. With that in mind you can select the first row in the table, hold shift on your keyboard, then select the last row of the table to select all the rows at once.
Hope that helps!
I see you have a searchbox in this example. I'm experiencing some strange unexpected behaviour when I use a searchbox. On first load the items in the table dynamically filter out when I type a character (or multiple characters) using the "Trigger output - Keypress" on the input field. So far so good, however. Once 1 select 1 row in the table the focus of the searchfield gets "lost". Now i have to manually put the focus on the searchbox for every character i type. Do you happen to experience the same thing?
Hey there, I unfortunately experience the same issue. This is being caused by a cell in the table being selected (which you can tell once you click on a row that the cell has a black border). There isn't currently a way to clear this while staying on the same screen.
The only way I have found to fix this is to have something in your OnSelect property of the table that takes you away from the current screen. Think of something like selecting a row taking you to another screen to edit that row on a form. When you return back to your screen with the table, the cell should be unselected.
This also has a side effect of triggering the OnSelect of the table when you navigate back to the table screen, so you'll need to add two lines of code to your table:
1. In your OnSelect property, add "UpdateContext({ctxTableFix: true}); UpdateContext({ctxTableFix: false})". This creates a context variable and sets it to true, then immediately sets it to false. You can put this after whatever action you take in your OnSelect property, so if you're navigating to a different screen you could put this after your navigate function.
2. In the Items property of your table, assuming you're using a filter function on a data source, you'll want to add the following as one of your filter function arguments:
"ctxTableFix = true || ctxTableFix = false || IsBlank(ctxTableFix)"
This will cause the table control to refresh itself when ctxTableFix changes in value, so basically it will unselect the row that you clicked on since it sees the value changing to true then back to false. This will stop the OnSelect function of the table from being triggered when you navigate back to the screen containing your table.
I know that's a lot of hoops to jump through but I hope that helps!
@PowerAppsGuy not as crazy as ChatGPT though. It's workarounds for similar problems are using timers, it proposed timers for double click action on a row as well 😅 But thanks for looking into it. I'll try and describe the problem as well as I can to MS support.
Same functionality in combination with the classic table does work as you'd expect it to.