This content has been marked as final. Show 5 replies
See here: http://docs.oracle.com/cd/E23943_01/doc.1111/e10978/c04_metadata.htm#sthref141
For dependency search for Dependent Choice List, then check if you can present it in a form of a tree and if so how it behaves.
Thanks for your reply Jiri,
but what we need is the mix of both options. We're able to build dependent simple option lists, but we need a tree which can be filtered (pruned) by other field. Is it possible?
In the Configuration Manager, when you select the "use tree" option, the "is dependent field" is enabled, so I understand that it is possible to do.
I have just checked it in the system, and unfortunately, the result is negative.
The reason seems to be that as soon as you 'Use Tree' for an option list, the system is unable to recognize relationship between the dependent field and the field on which the field should depend.
What have I tried?
a) defined two tables Countries (CountryID, CountryName), Cities (CityId, CountryId, CityName)
b) define two views for the tables above
c) defined a relationship binding the two tables on the CountryId column
Now, I defined two new metadata fields, Country and City.
- Country uses the CountryView (as 1st level of the tree),
- City is also defined as 'Use Tree'. I tried two options:
a) CountryView for Level1, CityCountryRelationship for binding Level1 and Level2, CityView for 2.
It works fine only as soon as I try to define the field as 'Dependent' on Country it tells me that 'You need to define a relationship for a dependent field'.
(This is understandable - the system will store value like 'CZ/Prague' or '1/2' and now such value exists in any column)
b) CityView for Level1
This even auto-selected the relationship for me, lets me to save my configuration, but when I open the definition, the relationship field is blank (!!!) again, and indeed, the system does not use the relationship.
Besides, b) is not exactly a tree, is it?
So, I conclude, the OOTB Tree-like fields cannot be made dependent.
I've made the same conclusion...so I think it's a kind of bug, or maybe the "is dependent field" shouldn't be enabled when you use a tree-like field.
Now, I'm thinking in doing some kind of customization...like changing the Root for the tree dynamically. Do you know if I can pass this as a paramenter on the service call? Or change the template SCHEMA_BROWSE_POPUP?