Wednesday, March 24, 2010

Removing a LOV return value leaves garbage in view object (Fixed in 11.1.1.4)

We had a strange bug that was really hard to find. We found some garbage in View objects that we could not find out how they were created. Yet I manage to reproduce it by removing a return value from Edit List of values wizard. In more detail :

When you have an LOV with 1 return value then the xml in the view object is like:



When you add a second return value from LOV by edit wizard:



Then the View object XML is like:


If from the same wizard I remove the second value then unfortunately the xml does not return to the initial state. It still has the DerivedAttrNames :





This causes various bugs in interface that are not easy to find, since nothing is displayed in log:


The workaround is to remove garbage by hand from xml.

Test case:

5 comments:

  1. Thanks nice post...it will definitely help someday

    ReplyDelete
  2. Filed Bug 9508282 - LOV: DELETING 2ND DERIVED ATTR CORRUPTS METADATA, GIVING ARRAYINDEXOUTOFBOUNDSEX

    Thanks for reporting this.

    ReplyDelete
  3. Bug has been fixed in our MAIN branch. Work through worldwide support to request a backport if needed.

    ReplyDelete