Repeating group cell item change

The repeating group’s elements are unrelated to the item that happens to be in that cell.

For example, if a RG cell has 4 sections that each show/hide based on the contents of their’s cell’s thing, then the FIRST time that cell loads up the elements will display correctly. However, if the RG’s list changes (like by adding a new item to the beginning) that will shift all of the items down one cell. None of the cell’s elements will update to reflect the new data in the new item.

Is there a way to force the RG cell’s elements to refresh when the item in that cell changes?

Seems like changing the thing in a cell should be equivalent to a page load, or something like that. The cell should reevaluate its own elements from scratch. @emmanuel @josh

Or, alternatively, is there a way to force a repeating group cell, or a reusable element, to refresh its elements from scratch as if there was a new page load, but without reloading the whole page?

1 Like

Hey @blueback09, did you find a solution for this? I’m experiencing the same problem: I have a bunch of reusable elements that are empty on page load and then they start to load info once the user has done some action. The problem is, to see these new content reflected in the repeating groups, I have to refresh the page, which is a bit of a bad UX. Any ideas? :smiley: Thanks a lot!

I’m having a similar problem when I have a RG receiving data via Bubble SQL plugin. On page load the data displays fine.
I have a button that changes some data. This same button has a workflow action to display list in RG containing the same query as is present with the original page load. The idea being to rerun the SQL query so I can update the RG with new data.
Well, the RG does not update visually, the underlying data does though.
This is evidenced by a note on inspect that says “The list of RGXXX of this element has been modified by an action …”
So how do I get the RG to update? I know I have received the data. I’m just not able to get the RG to refresh…

So on further investigation it seems if you request data, unless there is a variable that changes in the submission request, you’re just going to get the cached data from bubble even though it says the underlaying data changed. Adding a second “ghost” variable that changes on every request triggers bubble to make a fresh call. Hope this helps someone.

1 Like