I have a repeating G that has fields name and order displayed, I need user to reorder the data, I use arrows (tried also draggable element), order is changed only visually ofcourse , when i try to update the data to xano db I cannot access current index or anything related to the new order. note: I am still using the free plan.
Hi @maha.salemezzat . May be real time updated not affected your data
hi amer…I don’t understand what you mean
Hi @maha.salemezzat , how are you?
Xano can be tricky sometimes, can I ask why you are not using the bubble DB? It would make things insanely easier.
With your Xano DB and the order, how do you have the order setup within Xano? Is it just the default order or do you actually have a number assigned to each row for the order
Hi pattokane…I prefer using a relationship db and apis I have somehow complicated and big design , for the order i have a db field for order so when user changes the order of records i update this field for the records he changed. I said i can use current cell index for repeating group bec when user changes the items by arrow the correct order is the that of what’s displayed infront of him (cell’s index )
The problem is not with xano…the problem with bubble… no ability to access current cell index when i try to send the array coming from the repeating group or its custom state
I would be more than happy to jump in and have a play around with it to see if I can fix it for you, if you are ok with that
no need to bother yourself , I will put the screenshot , I just need instead of the part “this getPipelineStagesbody’s order” the current index of repeating group
I’ve run into similar issues with repeating groups in Bubble where the order of values shifts unexpectedly. It often comes down to how the data source is sorted or updated. Adding explicit sorting rules or using unique IDs to anchor each entry usually solves it. In some cases, saving the order in the database is the safest way to keep things consistent.
This topic was automatically closed after 70 days. New replies are no longer allowed.