Tried the above logic,( without putting the fields within containers) and it did not work, just shows the select option and hides the rest on load and on dropdown select @mayursatav
@mayursatav got it working. The problem was that the coralui components have a different way to address class and granite data ,
eg:
solution
1. below res type Needs granite:class property at the node containing granite/ui/components/coral/foundation/form/pathbrowser and granite data as a child of the node
2.granite/ui/components/coral/foundation/form/pathbrowser Needs "class" property at the node containing the res type granite/ui/components/coral/foundation/form/pathbrowser and property you would place within granite:data to be contained within the node itself
Pending issue as i see is inheritance- perhaps cause of deep nested, the inheritance is broken and i will raise a ticket with adobe on this. If LC has a content and you break inheritance, and rollout , the contents from blueprint overrides content at LC.. odd since inheritance is broken.
Another issue: add an item , select a value from dropdown and set the data for the field displayed, now add a new field and it strangely erases or overrides previous entry
Is there a way to group an option without even putting it into multifield ? Unable to group it.This is so that only one inheritance link icon is displayed and not more
