Advanced Analytics - Identity Configuration

Which IIQ version are you inquiring about?

Version 8.3

Share all details related to your problem, including any error messages you may have received.

Good morning!
We had recently made a change to the Identity Configuration file for a specific attribute (terminationDate). I believe this is an extended attribute, and was originally set as a string type in Identity Configuration and the hbm.xml file. What we wanted to do was to set this as a date object to solve a particular problem - the terminationDate attribute on an identity cube and the Edit Identity page would be presented as a string, so when changes were saved, this would set the terminationDate as a string (which is supposed to be a date object on the identity object). There are a number of processes that rely on the terminationDate being a date object, so what we did to remedy this is to set it to a date object in the Identity Configuration file. This worked well, at first - we saw that when editing an identity cube, the attribute was presented as a date (date picker) - same on the Edit Identity page. Now what we’re seeing is that in Advanced Analytics, when we select terminationDate as a field to display, that attribute is not shown at all.
My question now is besides Identity Configuration, where else would an attribute need to be changed so that it shows up on Advanced Analytics? I tried editing the hbm.xml file in a sandbox environment, but when trying to open an identity cube that contained a terminationDate, it errored out and wouldn’t open the cube.
My gut is saying that simply updating the Identity Configuration file is only one piece of the puzzle. Any ideas?

Identity Attribute Type is String or Identity, I believe it would good to keep the terminationDate as String and update the other processes to use string terminationDate and convert that to Date object whenever there is any operations needed as Date.

Hi @RSanders,
As Hemant mentioned you can set the Identity attribute type as String or Identity only.
you can always convert date format to string or vice versa using the below imports in your rules

import java.text.SimpleDateFormat
import java.util.Calendar
import java.util.Date;
SimpleDateFormat formatter = new SimpleDateFormat("dd/MM/yyyy")

That is actually the direction we’re going. There’s only a couple of processes that depend on the terminationDate, so rather than trying to find a way to keep it as a ‘date’ object, it’s easier to parse the terminationDate and convert it to a date in the process.

Thanks!

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.