Hi,We have an object, which consist of many attributes. One of the attributes for example COST CENTER needs to be made to accept only unique values. Can you please let me know how it can be done?
You could have a dynamic (NSQL) lookup for that field which only presents to the user un-used values from your list of cost-centres.
You would need to use the BROWSE_ONLY construct in the NSQL to ensure that already-selected values are displayed OK too.
Thank you very much David!
Is there anymore possible solution apart from the one mentioned?
Not that I can think of ; it has always be very hard to get any "validation" into the user-interface which is more sophisticated than it allows by default (simple ranges etc).
You could just allow whatever data-entry you like and then report upon it afterwards ; perhaps a process that picks up the duplicate and sends an email / warning message or just a simple portlet available to administrators to pick up the problem and manually address it somehow.