Very Helpful, thank you very much I really need the coloured option set in the current project I am working on but I don't need the sub-grid. Like in my case the sub-grid will cause a big issue Is there a way to achieve this??
Looks like you have to choose a child table for the nested subgrid. But if I want color only on those choice fields, is there another component that can be used?
@@PragmaticWorks Thank. The dropdown field in my case is the "status reason" default column in the table. I verified the column is not locked in the form. In the app view the colors work and I can edit the dropdown by opening up the row to edit, but it remains locked in the main view. Maybe the built in "status reason" has different logic behind it?
![Hands-On Power Apps Tutorial - Beginner to Pro [Full Course]](http://i.ytimg.com/vi/rJsHc-4w60g/mqdefault.jpg)
Thank you Brian - Really Appreciate your videos
My pleasure!
Very helpful, thanks!
Pragmatic Brian keeping me sane during and after the hurricane..man thanks!
LOL Living in FL i can fill ya. Thanks!
Very Helpful, thank you very much
I really need the coloured option set in the current project I am working on but I don't need the sub-grid. Like in my case the sub-grid will cause a big issue
Is there a way to achieve this??
Exactly what I've been looking for! Saved me from from building a custom page, thanks for the tip!
Glad I could help!
Looks like you have to choose a child table for the nested subgrid. But if I want color only on those choice fields, is there another component that can be used?
Followed this and in my app when I try to change the dropdown I get "this cell is not editable". Why are some cells editable and others not?
Make sure the field is unlocked. You can right click on the card to do so.
@@PragmaticWorks Thank. The dropdown field in my case is the "status reason" default column in the table. I verified the column is not locked in the form. In the app view the colors work and I can edit the dropdown by opening up the row to edit, but it remains locked in the main view. Maybe the built in "status reason" has different logic behind it?