Share all details about your problem, including any error messages you may have received.
Do we have to update hibernate file and modify DB when creating multi-valued searchable identity attribute?
I’m aware that once we use all 20 available extended attribute, we can create named extended attribute by updating corresponding hibernate file and running DDL script to make changes to DB and restart the application server.
But someone mentioned that if we want to create multi-valued searchable attributes, then we don’t need to make any changes to hibernate file or run DDL script.
Is this how it works?
I have done that many times and I’m familiar with the process.
I think you got my question wrong here. Let me clarify.
My question is - when creating multi-valued searchable attributes, it doesn’t seem like we need to update the hibernate file and run DDL script.
I tested this in our UAT by creating a new identity attribute and marked as searchable without updating hibernate file/DB. It resulted in an error displayed in UI.
But when I created another one and marked as searchable as well as multi-valued, it didn’t throw any error on UI.
So I just wanted to confirm whether if this is how IIQ works.
You are correct. If we mark an attribute as searchable and multi-valued, the system may not retain the settings. You can examine the details (these attributes are not marked with an extended number) from the Debug page → Identity Configuration. Upon re-opening and checking, you will observe that the searchable checkbox will be deselected, so this could be a bug.
its not a bug , the field is not index so it will revert back to just an extended attribute until you create an index for it in the database and map the hibernate identity object
