Hi,

Is it possible (without altering the templates) to change the default sort order for lazy-loaded related collections in the self-servicing scenario?

Suppose I have a customer-invoice one-to-many relation that by default has to be sorted on the 'Ordinal' field of the invoice, and I access my invoices like this:

CustomerEntity customer = new Customer(1);
InvoiceCollection invoices = customer.Invoices;

I'm still using LLBLGen 1.0 targeting .NET 2.0 using partial classes

Thanks...

Use SetCollectionParametersInvoices in CustomerEntity for this

Thx...

Which would be the best override/event to set this parameter by default, OnFetch?

        ///<summary>
        ///
        ///         Called right before the entity's Fetch logic is started. 
        ///         
        ///</summary>
        ///
        protected override void OnFetch()
        {
            SortClause sortClause = new SortClause(InvoiceFields.Ordinal, SortOperator.Ascending);
            SortExpression sortExpression = new SortExpression(sortClause);
            this.SetCollectionParametersTemplateSteps(0,sortExpression);
            base.OnFetch();
        }

It depends if you want to sort them at client side using the EntityCollection.Sort() method. Or you want them sorted when fetched from the database.

OnFetch seems a good candidate for the second case, but take care it would be executed every time you fetch the entity.

Walaa wrote:

It depends if you want to sort them at client side using the EntityCollection.Sort() method. Or you want them sorted when fetched from the database.

OnFetch seems a good candidate for the second case, but take care it would be executed every time you fetch the entity.

I see, I do prefer a server side sort.

Preferably I'd do it in the constructor, but I can't override the constructor since they're in the generated partial class part.

Walaa, can you please advise which method would be better? otherwise I'll stick with OnFetch.

Otis wrote:

Use SetCollectionParametersInvoices in CustomerEntity for this

Is there a similar method to add a standard predicate (filter) for these related methods, for example to filter out all entities where deleted=1?

Thx

No there's no such a method. You can specify the filter to a GetMulti... () overload though, which will fill the related collection, so for example you can call myCustomer.GetMultiOrders(...) to fill myCustomer.Orders and pass a filter to the GetMultiOrders overload to filter the rows you want.

Otis wrote:

No there's no such a method. You can specify the filter to a GetMulti... () overload though, which will fill the related collection, so for example you can call myCustomer.GetMultiOrders(...) to fill myCustomer.Orders and pass a filter to the GetMultiOrders overload to filter the rows you want.

Thanks!