We are getting 2 different dates from a source (Last logon from AD)
We want to compare it to take the most recent one and set it in a dedicated third custom Identity Attribute called “Last Login”
This part is working fine, but we have encountered a “side effect” which is we can’t do any date-type queries on this field in the “Search” module (e.g. attributes.lastLogin:<2022-01-01 returns all the Last Login dates)
In the documentation it is said that we need to add a dateType attribute to the end of our attribute name, which seems a bit odd …
Is this the only solution to achieve this ? Can’t we set an attribute type in another way ?
If yes, would it be possible to add the “dateType” to the technical Name of the attribute only (not the Display Name) ?
Currently this is the only way to setup the attribute. only “endDate”, “startDate”, and fields named with suffix dateType, DateType or datetype will be indexed as a date and be searchable using range.
You need to add dateType anywhere in the name or at the end. Search uses technical name of attribute & hence adding it into technical name will work fine.
Yes, you can use below API to update the technical name of the identity attribute. You will have to update the identity profile after doing this. Also the dateType indexing takes time & it will take some time to start showing up in search.
API
POST /cc/api/identityAttribute/update?name=
where = .api.identitynow.com
name= = current technical name of the identity attribute
Json Body: Replace name with the new technical name
To get the identity attribute list:
GET /cc/api/identityAttribute/list
To get a particular identity attribute :
GET /cc/api/identityAttribute/get?name=
I have similar requirements, I need to calculate identity end date , which is going to be the farthest value out of {(attribute1, source1),{attribute 3, source 2),{attribute 3, source3)}.