I met an issue when making a change to an existing dynamic lookup.
The lookup is named Browse Resource, and it is User-defined. It uses a dynamic query to find the resource by name.
The change i was trying to make is to modify the query to fulfill the coding rules for use with DWH. Please refer to below artical for the changes detail if needed (in the attached snapshot i highlighted the changes also).
CA PPM Tech Tip: Including Dynamic Query Lookup Attributes in the Data Warehouse
After modification, there is no save/save and return button, so i just clicked on continue. It led me to the next screen which is the Parent Window, from where i have a Save and Continue option. But after click on it, i checked the query again it remains the same as before..
What am i doing wrong here? Or is it true that i need to delete all fields that using this lookup, then i can edit it?
Thanks in advance for your help!
In more recent versions of Clarity, you cannot update the Query on a Dynamic Lookup once it is being used by an attribute. As Urmas suggested, you'll need to XOG out the lookup, update the query within the XML, and then XOG it back in.
Maybe your are out of luck.
Other people have had problems as well, but not all.
Dynamic Lookup error - Can't update lookup as it's either system or in use.
Small question regarding the provided screenshot.
I can see the error message, but I don't see the whole query.
Do you have "WHERE @FILTER@" in some point on the end of your query?
Sometimes this error don't come up when creating a query until it's relevant on some conditions.
Using WHERE @FILTER@ in lookup give you the option to use filter in the lookup browse window.
There are two 'Browse Resource' look-ups, one is 'user-defined' and the other is 'system restricted'. The 'user-defined' one should be edited but as urmas indicates, there are some versions of PPM which prevented users from editing any look-up if it has been defined on an Object Attribute.
Regardless of the above, modifying a OOTB look-up may result in the look-up being recreated in future upgrades.
Why can't you create a custom version of this Look-up which you know will not be overwritten