I wanted to deactivate one particular lookup. but before doing that I wanted to check how many objects are using this lookup.
Have you checked this ?
Have you checked this ?
Actually that thread didn't have the answer - I have just added something to it though.
@Pragya - have a look, theres some NSQL that you can build a portlet from that will work it out (you should also cover any portlet usage I think)
Hello David, NJ
Thanks for the replying.
The query in the provided link proved useful for us. We were able to find at how many places, same lookup is used.
I have one more query - One object is having a lookup (which is non-editable) and I would like to change the lookup to new one. Since it is non-editable i'm not able to change the lookup in the attributes; even I updated the LOOKUP_TYPE in the odf_custom_attibutes table in the back-end, but the lookup name did not reflected and it remains the Old one in the application. Is there any other way to do that?
if its non-editable then it is a system-restricted attribute ; you should not be trying to change anything about it, you will break Clarity that way (well, at least you will break your CA-support agreement!)
i.e. If you want to use your own lookup with a system-restricted attribute ; then you can't - you need to create a new custom attribute to replace the system-one and use that attribute "everywhere" in your application instead of the system-one.
Thanks for your reply, I'm sorry David, I forgot to mention that the non-editable Lookup is a custom lookup and is used for a custom attribute; we are trying to replace with the new lookup which is also a custom lookup.
Delete the custom attribute and recreate it using the new lookup.
(its your job to ensure that you save any data / do any data migration)
This attributes are used in one or more pages, so delete this attribute will again make an impact. So, is there any other way to do that from the back-end?
Not in any supported manner ; Clarity is stopping you from doing this (changing a lookup defined against an attribute) as it can not guarantee that your new lookup will preserve existing data that your old lookup might have provided. The supported way is to replace the attribute (and migrate the data). The application will tell you which pages it will be removed from, its not a complicated matter to add the replacement attribute back into them.
Retrieving data ...