Sorting within a collection with a Table View on a date range brings up unexpected results
I have a date property for an object where I specified that the range is optional. I use this property in a Trip planner where some dates are fixed for example a flight and some are ranges say a stay in a hotel.
I wanted to order the collection so that it is by date and adate without a range say 8th March appears after a date with a range of 8th-9th March
In order to get around this I had to create a number property for each ogject to preserve my trip in sensible itinary order.
2 Comments
Sign in to comment
Thanks for the clear description and workaround you found. Right now, sorting doesn’t distinguish between single dates and date ranges in the way you describe, so your result is expected with the current date property behavior. I’d recommend keeping this ticket open as a request to refine date/range sorting in table views so itineraries like yours can be ordered more intuitively without extra number properties. You can read more about date properties and ranges here: https://docs.capacities.io/reference/dates-and-daily-notes and table/collection views here: https://docs.capacities.io/reference/glossary#collections.
Hi, thanks for your feedback! If you scroll to the bottom of the Capacities settings, you will find the current version (e.g. "Capacities v1.3.14"). As soon as you click (or tap) on this text, all the information that is relevant for us will be copied to your clipboard. Please paste this information as a comment into this ticket. Thanks!
I Understand. I would also like to comment on this process. I reported this behaviour as a bug and it has been re classified as an improvement. I am ok with that but I did not receive any notification that it had been looked at and I had to come back here to search for it. I suggest that this process could be improved so we can follow through with the suggestions or bugs we find.