Is there any way to keep an expansion indicator from showing up if the child records are not ones the user is supposed to see? I added a cross reference table and XamDataCarousel including it in the hierarchy because of the Foreign Key relationship I set up between it and a table already in the hierarchy.
I just want two levels in this XamDataCarousel, the parent groups and the child records associated with each group.
Joe Modica "]With this in mind, instead of the approach shown in the sample code above where we let the control generate all the Fields and then manually hid the Field we didn't want, we could have taken the reverse approach and set AutoGenerateFields to false and then added Field objects just for the Fields we want to be included.
Yes, I finally stumbled on to this, including having separate FieldLayouts for the Parent and Child records so that the Carousel would find and use each separately when appropriate. Like most things it seems straightforward in retrospect, but I didn't see it for awhile.
<igDP:XamDataCarousel.FieldLayouts>
<igDP:FieldLayout>
<igDP:FieldLayout.Fields>
<igDP:Field Name="ChildDataField" Visibility="Collapsed"/>
</igDP:FieldLayout.Fields>
</igDP:FieldLayout>
</igDP:XamDataCarousel.FieldLayouts>
</igDP:XamDataCarousel>
"joem" wrote in message news:11797@forums.infragistics.com... Hi Mark - Yes - you can achieve this by creating a FieldLayout that hides the Field that represent the child level you want to hide. For example:<igDP:XamDataCarousel x:Name="myDataCarousel"></igDP:XamDataCarousel> <igDP:XamDataCarousel.FieldLayouts> <igDP:FieldLayout> <igDP:FieldLayout.Fields> <igDP:Field Name="ChildDataField" Visibility="Collapsed"/> </igDP:FieldLayout.Fields> </igDP:FieldLayout> </igDP:XamDataCarousel.FieldLayouts> </igDP:XamDataCarousel> Note that the FieldLayout.Settings.AutoGenerateFields proeprty defaults to true by default and causes Field objects to be created and added to the FieldLayout.Fields collection for all fields discovered in the data. With this in mind, instead of the approach shown in the sample code above where we let the control generate all the Fields and then manually hid the Field we didn't want, we could have taken the reverse approach and set AutoGenerateFields to false and then added Field objects just for the Fields we want to be included. Joe Modica Joe Modica [Infragistics]New York, USA http://forums.infragistics.com/forums/p/1257/11797.aspx#11797
Hi Mark -
Yes - you can achieve this by creating a FieldLayout that hides the Field that represent the child level you want to hide. For example:
Note that the FieldLayout.Settings.AutoGenerateFields proeprty defaults to true by default and causes Field objects to be created and added to the FieldLayout.Fields collection for all fields discovered in the data. With this in mind, instead of the approach shown in the sample code above where we let the control generate all the Fields and then manually hid the Field we didn't want, we could have taken the reverse approach and set AutoGenerateFields to false and then added Field objects just for the Fields we want to be included.
Joe Modica