Search Identity Attributes using Relative Date Comparisons

[wvandeus (William VanDeusen)]

I’m having trouble Searching Identity Attributes using Relative Date Comparisons.

Fact number 1)
I’m able to search for my attribute “searchEndDate” (which is in ISO8601 format) using an exact value of January 8th 2024 (keep in mind, that date value is within this year, around 250 days ago)

Fact number 2)
I’m able to search for accounts “created” (which is a different built-in attribute I think?) using Relative Date Comparisons, this will gather any created in the past year (365 days)

Fact number 3)
The Sailpoint documentation suggests this is supported, it even has an example which shows “Identities with an endDate attribute set to within the next year”

The problem)
When I search for my previously mentioned “searchEndDate” attribute using Relative Date Comparisons (any searchEndDate in the past year 365 days) it’s finding no results. At the very least, it should be finding my Fact-number-1 which was 250 days ago.

If you need more information, like if you want a screenshot of the transform setting my ISO8601, or something else.

Or if you have suggestions or other things to test, I’m happy to hear it.

[liamkokeeffe (Liam OKeeffe)]

Hi William,

In order to do relative date searches, the attribute must be a default date attribute (eg. endDate, created, etc) or the technicalName of the custom attribute must end with ‘dateType’. Try modifying your current attribute technicalName from ‘searchEndDate’ to ‘searchEndDateType’.

There’s a brief section in the ISC Admin Guide under the Search tab on this.

Thanks,

Liam

[wvandeus (William VanDeusen)]

Thank you, it worked!

(just to clarify for anyone else reading this later, you actually have to create a new attribute with the words dateType at the end of new attribute name. I originally thought Liam was saying I could just search for my existing attribute with the words “dateType” added in the search screen, but that’s not how it works)

[liamkokeeffe (Liam OKeeffe)]

Sorry for the confusion there, but glad it works now!