Details/Edit Screen from Nested Gallery

[CarlHRVA]

Hello,

I have two galleries, one nested inside of the other. The top-level gallery, Gallery1, is displaying items "Grouped" by "Status" using the distinct function (thanks @wyotim, I am using your solution again in another application already) and the nested gallery, Gallery2, is expanding or contracting to show the items with that particular "Status" when clicked. This looks and functions pretty great but the issue I am having now is that when I add icons/buttons to the Edit or Details screen, it is not displaying any of the data. I was using the same setup before nesting it and it was working as intended and I haven't been able to find anything about how to overcome this issue. Any help would be greatly appreciated!

[wyotim · Accepted solution]

Hey @CarlHRVA! Am I understanding correctly that you are trying to click on the button/icon and get the data from that item to another screen to view or edit it? What code are you using to get the item's data? Assuming I am understanding correctly and you aren't trying this already, I would suggest using a variable to store the item's data to bring it into the other screen like so: 

// For a local variable (one that can be used only on the screen it is in)
Navigate('My Screen Name', ScreenTransition.None, {varItemData: ThisItem})

// For a global variable (one that can be used anywhere in the app)
Set(glbItemData, ThisItem);
Navigate('My Screen Name', ScreenTransition.None)

You can then use the variable name (glbItemData or varItemData) to reference the item in a form's Item property or in the controls you are using if you made a custom form (e.g. varItemData.FieldName). Nesting the galleries can cause trouble with a few things and referencing the data in them is one of those areas. I'm actually not sure if it is a fully supported methodology but I use it quite a bit and it generally works great once the kinks are ironed out.

On the very possible chance that I am not fully understanding your issue, feel free to help me with where I am going astray! Cheers!

[CarlHRVA]

@wyotim Brilliant! Thank you as always. I spent the last 2 hours trying to use a collection but a variable is working great. I do have one other issue I don't really understand. For all of my dropdowns/comboboxes it doesn't like anything I've tried or if it does it doesn't display the data. I'll show some screenshots, maybe you could point me in the right direction there as well? I very much appreciate all of your help, you are an absolute life saver.

[v-siky-msft]

Hi @CarlHRVA ,

Have your issue been resolved? If not, happy to help further.

From the snapshot, we can see that the output of varItemData.Product is Table, so you can try to use First(varItemData.Product).Value to display in Label.

Hope this helps.

Sik

[CarlHRVA]

Thank you for your help! Unfortunately, this doesn't seem to work for me. Any idea why? Also, what about those with a data type of Record? Thank you again, would love to have this resolved and understand how to handle this in the future.

[CarlHRVA]

Okay, so this DOES work to display it in the label. Is it possible to display this in the dropdown as this is an edit screen? Does it matter if my data source values do not match what I am trying to populate the dropdown with?

Thanks,

Carl

[wyotim]

Hey @CarlHRVA, this is a question I should have asked sooner but what data source are you using? SharePoint? I noticed that some of the time the variable reference is showing as a record and others as a table. I am guessing that there are some complex data types in each record, which is probably where these issues are coming from. As @v-siky-msft so keenly observed, for the fields that are returning a table of data, using First(...) should help, though you might need to use something other than Value, depending on the structure of your data. 

As to whether it matters if your data source values match what you are trying to populate the dropdown with, yes it does. There needs to be some commonality so that the dropdown can recognize the value being stored in the record both to write something useful when the record is updated as well as to recognize the default item in the record. Depending on the structure of your data, this could be a line of text, an ID from a table of data, etc. Complex data types in SharePoint work a little differently than the more common types like text and numbers. I'm not too well versed in them as we don't use SharePoint where I work so I'll need to read up a bit if those are being used. 

Could you share what you have in one of the Item sections of your dropdowns and how that data relates to the field in the record? It could be different for each one, so feel free to share if there are different scenarios. Also, could you share what the error is that it is giving when you try to use the varItemData.Something as well as the First(varItemData).Value? We'll get this sorted yet! 

[CarlHRVA · Accepted solution]

Thank you both for your help, as always. Yes, this is using a SharePoint list as a data source and what I ended up doing ( and should have thought of sooner/on most of the apps I've worked on😑) is allowing PowerApps/SharePoint to generate a test app for me and then seeing how that app handled each field on the edit/display screens. Although your answer to my original question was the solution I was after (to use a variable because of the nested gallery), my secondary issue was resolved by setting the default value on the entire data card rather than the dropdowns themselves. Thanks again for your help!

[wyotim]

@CarlHRVA good call with the generated app! That can be a great way to see what is going on with things. I am happy you were able to get this sorted. 👍

[Powerappuser429]

Any solution found on this topic?