Hi, The issue is that when you assign var_B = var_A.list_of_B, you’re basically creating a static list on the page. Bubble can sort text fields easily in a repeating group, but sorting by creation_date or modification_date only works reliably when the source is a search result, not a pre-fetched list.
A common solution is to skip the intermediate var_B and do a search for Bs that meet your criteria, then sort that search by creation or modification date directly in the repeating group. Alternatively, if you really need to use var_B, you’d have to use the :sorted operator, like var_B:sorted by Creation Date, before sending it to the RG.
If neither :sorted nor using the list directly is affecting the order, it usually means Bubble is still treating the list as an already-loaded list from a single parent thing, which can ignore date-based sorting. One thing you can test is removing the list relationship entirely and instead pulling Bs with a Do a search for B where A = var_A, then sorting by creation/mod date in the RG data source. That forces Bubble to query the database rather than reuse the in-memory list.
If that works, then the issue is the list field on A — date sorting on nested lists can be inconsistent because Bubble preserves the internal list order, not the field values.
Not the prettiest workaround, but searching instead of using the stored list usually makes the date sorting behave correctly.
