EFDataSource Not Bringing Children or Related Entities

Hi Ta,
>>I have tried a new report and thrown an object at it
Would you please clarify how you're filing your report with data? Are you using any component for this purpose? Please share the definition of your DBContext and all relevant entities. Based on your description, I imagine we have a situation with the EF's Lazy loading feature disabled. In this case, nested navigation properties won't be loaded unless you include them explicitly to the query with Include().
I look forward to your reply.

Regards,
Yaroslav

Sure,

My context is simply

C#
public class MyContextFoo : DbContext  
{  
    public MyContextFoo() : base("name=myappname")  
    {  
        Database.Log = p => Write(p);  
    }  
    public DbSet<SaleDepartment> SaleDepartment { get; set; }  
    public DbSet<SaleGroup> SaleGroup { get; set; }  
    public DbSet<SaleText> SaleText { get; set; }  
    public DbSet<Tax> Tax { get; set; }  
}  

If within my MainWindow I place the following:

C#
var foo = new MyContextFoo().SaleGroup.Include("SaleDepartments.SaleTexts").Include("SaleDepartments.Tax").ToList();  

I get everything I require with Foo. However, the report has an DataSource of efDataSource1, and the DataMember of SaleGroup, which when I go to change this gives me the following image:

So it knows what to bring in, and the report layout is exactly what I'm after, but it's just not bringing in any children :(

Colin.

BTW. Ta is short for Thanks in the UK ;)

Looks like the images I pasted didn't work, here's the data member one.

And here's the report layout one.

>>However, the report has an DataSource of efDataSource1, and the DataMember of SaleGroup, which when I go to change this gives me the following image:
Are you saying that you're getting an error message about the wrong / missing DataMember? If that is correct, you actually need to wrap 'foo' into a fake class with one "SaleDepartment" collection property (to the match the exact schema against which your report has been designed). Also, I see that you're using our EFDataSource  component.  Are you saying that if you don't substitute it with a runtime collection, it does not produce any output for nested navigation properties? This behavior is unexpected. Although EFDataSources handles this scenario in not a very effective way (a separate SQL query is sent for each master object), I'd expect to see all data in the preview nevertheless.

>>BTW. Ta is short for Thanks in the UK ;)
Alright, that was awkward, I though it was your name :) Thank for you clarifying this, Colin.