Nested gallery will not collapse when not selected (not visible)

[AmyF]

I feel like I'd solved this already.  I had an app, there was something fundamentally wrong with it as no patches of columns from the gallery would work.  I could patch a literal value, but was unable to patch any of the gallery fields which absolutely had data in them.

When I'd click a button on the page with the gallery to do the patch, if I examined any of the fields I was attempting to patch they were null within that gallery and I know this because I put them in a variable and they were null.  So again, it would patch a literal value like "Hello there" to say a single line text field but it would not patch txtInputNotes  which was the field name in the gallery.  Nor txtInputNotes.Text  nor txtInputNotes.Value.   I tried every way possible but it wouldn't text anything but a literal in quotes.

I cut it down so bare that I finally gave up and thought I'd have to build a new gallery.  duplicated the page, built new gallery from scratch (well it's a groupby situation so I built 2).   I don't know if I can patch yet, just trying to finish the gallery to the point I had it before.  Now this new gallery is not hiding the nested gallery items when the parent is not selected.  I'm trying EVERYTHING.  I checked a video to recall if I did something wrong and in the video the child gallery was hidden simply by putting an IsSelected in the Visible property.     Sadly this isn't working for me either.   I don't want to pound on this for days and days if there's something fundamentally wrong with this new set of galleries I'm creating.  And since I never give up, I will waste days and days until I finally just give up and try again.

ANY suggestions are welcome I'm at wits end and working on my vacation time.   very sad.

[Chris-D]

Patch( Data, Collection) shouldn't touch every record. I've checked my demo data from the example I posted before and it has only modified the rows that were changed.

To tidy up your list above, use the OnChange code that I posted before. If the ID already exists in the table of changes then it's updated instead of adding a new value. I found it helps to avoid confusion and mistakes, to ensure your list of changes is compatible with your data source, you can define the new record like this:

// Here, adding Penguins@ before the record ensures that the record is 
// compatible with the Penguins data source
Collect( GalleryChanges, Penguins@{
        ID: ThisItem.ID,
        Note: Self.Text
})

No need to start a new thread, you can mark more than one answer as the solution 🙂

[AmyF]

Oh that's good, we may have many solutions as we go...  This brings up my current problem (beyond this).  After I patch, the datasource is refreshed, I recollect it and the gallery reloads with the data I just patched.  That's great except after the patch, during the reload process, every OnChange action on every control in every gallery fires and fills up that table I was collecting (after I've already Clear'd it out.   So it just fills right up with IDs and older data that I've already patched and cleared out of that thing.   It's crazy.   I've read that this is a bug, but how can that be?  No one would use OnChange to collect the changes if it was so messy.   Are you aware of this error? I'm trying to come up with a workaround that would allow me to use the OnChange for this but so far, I'm at a loss (big surprise there)   😉

[Chris-D · Accepted solution]

This doesn't happen with my demo. 

Why are you collecting the data before the gallery? You should just be able to put whatever you're collecting in Gallery.Items? 

[AmyF]

once again your words are causing me to question things.  As I developed this, I put in extra code at the bottom of the patch button's onSelect.  I wasn't seeing my changes and sometime after that, I was so I just replicated that as my "working" copy throughout my app (GAH!!!)  So, I removed it and boom.  That's not happening now.  Thanks again.

[AmyF]

@Chris-D    So I removed the extraneous code to refresh and recollect everything and it was working fine... yesterday.  Today I get on, open the app and the entire gallery of IDs filled up again on every/many onChange fields with the IDs.   I don't get why those onChange events are firing during load.   I will see if I can put in a limiter to only perform the onChange if there is a change in field value, like you suggest.  Still seems very weird that those would fire on loading the app.  Also, and this didn't seem to be happening yesterday, if I clear that data out using a button I've put in, when in Dev, if I move from screen to screen, that screen's galleries populate and those IDs are recollected and display.  I didn't notice that yesterday and I'd have thought that I would have.   Anyway, my search for an answer to this continues.   Do you have any other insights on that?

[Chris-D]

I'm not seeing this at all on my test. If it's only happening when you switch screens, maybe check the OnVisible and OnHidden of your screens. 

Could the collection that captures your changes be a duplicate name from elsewhere in your app?