# Ranking and Data Storage **URL:** \ **Category:** Ask for Help\ **Created:** [April 24, 2025, 5:46pm UTC](https://community.glideapps.com/t/ranking-and-data-storage/81521 "2025-04-24T17:46:53Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [April 25, 2025, 3:41am UTC](https://community.glideapps.com/t/ranking-and-data-storage/81521/4 "2025-04-25T03:41:31Z")
At a basic level, you could use case number 2 in the following post. Instead of pointing the lookup at the entire table, you would point it at your sorted query. This works at a basic level, but gets complicated if you start to have ties. All depends on how you would expect ties to be handled. > [@How do I create an auto-incrementing row number with Glide Tables?](https://community.glideapps.com/t/how-do-i-create-an-auto-incrementing-row-number-with-glide-tables/39572): > > This is a question that comes up a lot, so creating this topic to use as a reference. Typically, there are two distinct use cases when it comes to auto-incrementing row numbers. Use Case 1: – We need to generate a Part Number, or an Order Number, or an Employee ID. Once the number is generated, it should never change, even if rows are deleted. – The general approach for this use case is to maintain a static counter, use it to craft a suitably formatted ID, and increment it by one every time… --- _[View the full topic](https://community.glideapps.com/t/ranking-and-data-storage/81521)._