Ranking and Data Storage

[Jeff_Hager]

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?

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…