It’s not a bug, it is just the natural consequence I think. As you said, the first “order” is unsorted (you can drag and drop for instance), so removing the Sort rules does not give you back any ordering.
What you could do is create a Created Time
field and sort by it, so you would have the “original order”.
It’s not a bug, it is just the natural consequence I think. As you said, the first “order” is unsorted (you can drag and drop for instance), so removing the Sort rules does not give you back any ordering.
What you could do is create a Created Time
field and sort by it, so you would have the “original order”.
Thank you, Elias!
Created Time field worked like a charm!
Autonumber field would work too
Thank you, Elias!
Created Time field worked like a charm!
Autonumber field would work too
Keep in mind while CREATED_TIME()
is persistent, an ajutonumber field can be changed. That is, if you sort a table and then change the configuration of a CREATED_TIME()
field to, say, a date field and back, the field retains its original values. If you change an autonumber field to number and back, it will renumber based on the new order. This can be a handy trick at times.
Keep in mind while CREATED_TIME()
is persistent, an ajutonumber field can be changed. That is, if you sort a table and then change the configuration of a CREATED_TIME()
field to, say, a date field and back, the field retains its original values. If you change an autonumber field to number and back, it will renumber based on the new order. This can be a handy trick at times.
It’s good to know. Thank you!
