We sort determinations in our collection by date descending, with the current determination and most recent determinations first.
We accomplish this by using this form xml:
A problem arises when determinations do not have a known determinedDate. The null value sorts at the beginnning of the set of determinations, even in front of the one marked “Current”.
Is there any way to make Null values sort at the end of the set, or alternatively, to add multiple hierarchical or conditional sorts (for example, sort first by determined date and then by x, or “if there is a null value, sort by recordID”)?
It’s frustrating because we often are adding prior determinations on old labels that don’t have dates associated, and if we add one without a date it sorts in front, ahead of the current determination.
Thanks for your question! At the moment, there is no way to make null values appear at the end of the sort, or to add multiple hierarchical or conditional sorts.
I’ve added a new GitHub issue for this request:
I can completely understand the challenge of having the null value records appear first. Thank you for reaching out so we can review on our end!