Data Explorer ObjectDataSource with Nested List View

[Peter]

Hi,

I have an ObjectDataSource with Collection as follows:

public class Person
{
    public string FirstName {get; set;}
    public string LastName {get; set;}
    public List<Email> emails {get; set;}
}

public class Email
{
  public string Address {get; set;}
  public string Category {get;set}
}

A method returns a List<Person> that is used as the datasource for the report

In the Report Explorer I see the fields FirstName, Lastname and Email
However Email only gives me Capacity and Count and not Address and Category.  It seems that the Data Explorer cannot drill down to the Nested list of Emails and its properties.

Is there a way to set it up so that the Email fileds are exposed Data Explorer?  This way I was hoping to avoid using subreports which will get a object datasource  of "PersonEmails" from a method and use this in the details.

Thanks,
Peter

[Elian]

Hello,

This isn't possible because the relation is one-to-many and Fields.Emails.Address wouldn't be a correct expression. What you can do is use a report item that supports data binding (like Table, Crosstab, List or SubReport) and set its data source with Bindings to ReportItem.DataObject.Emails which is the current DataObject (the current person's list of emails) and then in this table/crosstab/list you can use the expressions Fields.Address and Fields.Category.

Kind regards,
Elian
the Telerik team

[Tormod]

In my experience setting the databinding to the datasource property isn't enough to provide design time support within the data explorer if you, for example work on tweaking the innards of a list/crosstab using an ObjectDataSource.

I do it by creating a mock ObjectDataSource that returns the Email type and then assign it to the datasource property of the list. Then the data explorer will show correctly "Address" and "Category whilst you are working inside the list rows/table cells.

You basically set the DataSource property for the List/Tab twice. Both as a normal entry in the properties dialog and also through an entry in the "bindings" collection through which you bind "DataSource" to "= Fields.emails". Thus, the dataadapter set through the properties dialog will be overridden at runtime, but is still necessary to have support for field names at design time.

[Nuwan]

HI Elian,

I tried the way you explained and it is working fine. But I need to give sub List as a object list.

 I am using a LINQ query to retrieve all data one time.
How can I list my sub class list data with master class data in the report?
Please reply..

I meant, my class strcuture is as follows.

 public class POLevelDeliveryOrderHistory
    {
       
        public List<POHistoryDeliveryOrderDetail> DeliveryOrderDetailList { get; set; }

        public WorkOrder ParentWorkOrder { get; set; }

        public DeliveryOrder DeliveryOrder { get; set; }

        public Customer Customer { get; set; }

        public string WorkOrderNumber { get; set; }

        public double SumAmount { get; set; }

        public double SumQuantity { get; set; }
    }

    public class POHistoryDeliveryOrderDetail
    {
    
        public virtual DeliveryOrderDetail DeliveryOrderDetail { get; set; }

        public virtual DeliveryOrder DeliveryOrder { get; set; }

        public virtual int DeliveryOrderID { get; set; }

        public virtual int DeliveryOrderLineID { get; set; }

        public virtual double Quantity { get; set; }

        public virtual decimal? UnitPrice { get; set; }

        public virtual WorkOrder WorkOrder { get; set; }

        public virtual WorkOrder ParentWorkOrder { get; set; }

        public virtual int? WorkOrderID { get; set; }
    }



Thanks,

Nuwan

[KS]

Hi,

Check this Data Source Business Objects   

The way I do it is to add helper ObjectDataSources for each nested type and use them to make my Tables. When I am done I just change the DataSource to nothing and apply the binding to my main ObjectDataSource fields, and finally place the Table into the parent container.

- KS