Collapsing/expanding sub items in a list to hide redundancy

(1) Share

Report

Posted on by CU12051524-0

I'm having issues for modifications to items vs columns. My company uses lists to track our tools we send out for service calls, but since we track via serial number or inspection number, my list ends up like this:

description PN SN Sent to date sent by

hammer XYZ 111

hammer XYZ 112

hammer XYZ 113 italy 10/4/2024 john doe

hammer XYZ 114

level 180DV 9837

level 180DV 3733

what I want is to have ONE entry that can expand to show each serial number so you don't have to scroll through page after page of the same tool. I don't want to see the 50 hammers unless I click to expand the hammer, if that makes sense? I can't seem to find a way to do this. I thought maybe a drop down menu but those seem to be tied to a column not an item. And if I could make a drop down menu for each item, I'd need entries tied together. For example, John Doe can check out hammer SN 113 May 1st and Jane can check out hammer SN 111 May 10th, and the date checked out, name, etc are all linked so I can tell who has which hammer on which day. Is this even possible? It's so cluttered when every serial number is its own item equal to all others. And when all is said and done, we need to be able to still export the list of tools to create a CI.

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (0)

WarrenBelz 154,755 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @CU12051524-0,

There may be some possibilities here, but they will depend on the number of records in your list and to some extent your data source type. Can you please confirm both of these.

Was this reply helpful? Yes No
Suggested answer

Michael E. Gernaey 53,960 Moderator on at

Like (1)

Report
Copy link

Link copied!

Hi @CU12051524-0

As @WarrenBelz says the actual back end storage means a lot as it relates to possibilities.

What I have done in the past are of 2 options

1. (and I dont love doing this one btw) is a Gallery in a Gallery, where the outter gallery holds the parent. Essentially you would use a Distinct expression on the Description (so you only see Hammer 1 time)

2. You would use this to build your first Gallery

3. Inside that Gallery you would build each line items gallery by filtering meaning

Line 1 of ParentGallery - ChildGallery Foo

For the Child Galleries Items property

Filter(DataSource, Description - ThisItem.Description) or use ParentGalleryName.Description

This way they can expand and un-expand (wow is that a word.. doubt it lol) each line item. And your Child Gallery only shows the sub fields, not the word Hammer each time for instance.

Was this reply helpful? Yes No
WarrenBelz 154,755 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @CU12051524-0,

A quick follow-up to see if you received the answer you were looking for or if you need further assistance.

Please click Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it a Like.
MVP (Business Applications) Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No
CU12051524-0 4 on at

Like (0)

Report
Copy link

Link copied!

I'm not sure a gallery would still allow export to excel to create a CI?

the data entries are pretty extensive, 500+ items. some only have 1 of each type and some have 60. it's all text fields and 1 photo attachment for customs purposes.

Was this reply helpful? Yes No