As stated in the above post, new extended (identity and string type) attributes are added in identity mappings. These fields are used when submitting creation and edit form for non personal accounts (service accounts). When running the report under analytics, it does not show any values in the fields. Attached screenshots.
Under Identity object it stored as below. For report, I am using the advanced analytics with filter condition by selecting the check box near these fields in the Choose fields to display option.
Ok, I think you are not stored correctly those info.
I can see something strange.
Both obj managed IDNs butthe first one has identity like type and the second has string
the second have 22 like extendedNumber, theoretically SP can managed until 20 extended number attribute. If you have more, better if you change in namedColumn like extended attribute
the editMode is Permanent, it means that you can change the value only from source mapping and you havent it. Try to use Temporary.
Also, check if into DB are stored some info for those identities in this columns. I think with your configuration, SP saves those info into attributes and not in own columns(or not saves)
PS How you see those attributes on the identity from debug?
@vishal_kejriwal1@enistri_devo I have uploaded only the attribute part of Identity from debug. From the two attributes, one is of type IDENTITY and another one is STRING. Identity_xml.txt (1.9 KB)
in this case into identity is stored only the extended11 and it msut be visible into the report.
For the other one, I think the problem could depends for the number(22)
I got it @enistri_devo . Please let me know how to update the iiq schema after adding the attribute into the identity hibernate xml file. Hope it will reflect after the database schema update.
please read the documentation before.
Verify your DB configuration before change this, I dont know the situation of your DB and maybe you need to adjust that I write.
I even tried removing the column from sailpoint and as per the documentation the first step is to add the attribute into the hbm file, updating DB and then adding the attribute into identity mappings. I have followed the same but after loading DB and restarting the service, the sailpoint page is not loading and got the exception page. This prevents me from adding the attribute in the identity mappings. After removing the added attribute from the hbm file, SP is loading without issues.
After connecting with Sailpoint support team, I need to add run the stored procedure source add_identityiq_extensions.[dbms] after adding the extended attribute into the hbm fille. I am using SQL server and please someone assist me on how to execute the sql procedure. I tried like running a normal sql query but ending with error.