Hi Dan, Thanks for the quick response - will check out this option. Just curious - why is this restriction?
Thinking of a scenario - I can have 1 entity, having its properties populated at different stages of application process. For instance metrics for a project management software, will get filled, as the project passes from one phase to another, in a water fall model.So would it not be good, to have only one set of properties populated and the remaining properties be hidden... Leads to one more question - is it possible to multiple layout files for an entity Thanks & Regards Bharani On 2017-02-08 14:49 (+0530), Dan Haywood <d...@haywood-associates.co.uk> wrote: > No, IIRC a layout.xml is not valid unless there is exactly one region > indicated for all of unreferencedproperties/collections/actions. By design > to avoid confusion. > > One trick though is to create a column with span="0" and put those regions > (eg fieldsets) there. I just discovered this trick myself a week or so ago. > > HTH, > Dan > > On Wed, 8 Feb 2017, 10:04 Bharanidharan Srinivasan, <bharan...@gmail.com> > wrote: > > > Hi, > > > > Is there a way to have only the required properties of a domain object > > mentioned in layout.xml - is there a way to avoid inclusion of > > unreferencedcollection or unreferencedproperties > > > > Thanks & Regards > > Bharani > > >
