Been waiting for this feature for a long time as well.
From my experience working with Noloco tables, I wonder if this might be tricky for them to implement because of how record IDs and sorting currently work. Each record seems to have a sequential ID based on creation order (the first record is 1, the 300th is 300), and that ID doesn’t change even if records in between are deleted.
You can see this behavior in rollups and “find record” steps too, sorting defaults to latest created unless you explicitly build dependencies or additional logic. When trying to automatically find the nearest record above or below (for manual reordering workflows), it returns the first record found based on record ID rather than the closest match by provided value.
I’m not a developer and don’t know how Noloco’s backend is structured, just sharing what I’ve run into while trying to build workarounds. Would love to hear from the Noloco team whether this is something technically difficult due to architecture, or just not prioritized yet.
This feature would make managing ordered lists so much smoother. The use cases are endless.