In our Web Dynpro application we provide a generic search mask to the user. The information about the search fields like labels, length etc. is retrieved from the backend during runtime. Also, the information if there should be a value help available or not is read from the backend during runtime. In case there should be a value help for a search field we just add an OVS extension, using method WDValueServices.addOVSExtension(...). For this, we pass the AttributeInfo of all relevant context attributes to this method.
The problem is now the following: The user can switch between different kinds of search masks. Because of the generic implementation all use the same Web Dynpro context. So it might be that the search field #1 on the first input mask has a value help whereas search field #2 on the second input mask doesn't. But if we once have added an OVS extension to the context attribute of search field #1 it can apparently never be removed anymore. At least I couldn't find a method to remove it.
Hi Jens,
I'm not sure, but you can try the following:
1. use wdContext.reset(false) -- probably it drops OVS extensions.
2. if [1] doesn't work, then create search attribute(s) dynamically, then do wdContext.reset(false) and re-create search attribute(s) from scratch
VS
Hallo Jens,
the WDValueServices-API will be adapted to this need in NetWeaver 04 - Support Package 11.
Greetings, Bertram
Add a comment