Hello,

I'm trying to upgrade from v2.5 to v2.6, adapter version.

I've created a TypedList for a table called Sites which has a (1:n) relation to a table called Siteaddresses. The TypedList contains fields for both tables including SiteName and SiteAddressLine1, etc.

The relation has a description of: Site.Idsite - Siteaddresses.Idsite (1:n) - with a 'left' join hint.

The problem is that I want to see address information in the list only when Siteaddressess.Idtypeofaddress = 2, otherwise I don't want the address information to be in the list however I still want to see the site information.

When I apply a predicate expression like the following:

filter.PredicateExpression.Add(SiteaddressFields.Idtypeofaddress.SetObjectAlias("Siteaddresses") == 1);

The predicate will filter out any sites that don't have corresponding addresses of type 1; it becomes an inner join.

I had this working in v2.5 after posting a question here: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=14022

Now a week later I'm having this problem again.

Specifically, I'm having problems because the CustomFilter() method seems to have disappeared from filter.Relations[x] in v2.6.

So the line:

           filter.Relations[0].CustomFilter = new PredicateExpression(
                     SiteaddressFields.Idtypeofaddress.SetObjectAlias("Siteaddress") == typeOfAddressID);

Now generates an error.

I've tried casting the IRelationCollection as IEntityRelations as in:

IPredicateExpression customFilter = new PredicateExpression();
customFilter.Add(SiteaddressFields.Idtypeofaddress.SetObjectAlias("Siteaddress") == typeOfAddressID);

foreach (IEntityRelation relation in filter.Relations)
{
    if (relation.AliasRightOperand.Equals("Siteaddress"))
    {
        relation.CustomFilter = customFilter;
        break;
    }
}

And using the CustomFilter() there but, while this compiles and runs, it results in an Inner Join that doesn't work for me.

Any help would be appreciated.

Wm

William wrote:

And using the CustomFilter() there but, while this compiles and runs, it results in an Inner Join that doesn't work for me.

Did you add the relation as JoinHint.Left?

Could you try this way?

lol, thanks for the help but you linked back to one of my prior posts which was for a prior version that doesn't work anymore.

William wrote:

lol, thanks for the help but you linked back to one of my prior posts which was for a prior version that doesn't work anymore.

Haha funny.

Anyway, I have a test working on v2.6 with that approach. Please post the code you are using and the error.

I'm confused then.

I couldn't get the code:

IRelationPredicateBucket filter = sites.GetRelationInfo();

for (int x = 0; x < filter.Relations.Count; x++)
{
        if (filter.Relations[x].AliasEndEntity.Equals("Siteaddress"))
        {
            filter.Relations[x].CustomFilter = new PredicateExpression(
                     SiteaddressFields.Idtypeofaddress.SetObjectAlias("Siteaddress") == typeOfAddressID);
            break;
        }
}

To work in v2.6 because the property: filter.Relations[x].CustomFilter doesn't exist when using the indexer.

What I finally got to work (I haven't finished testing yet) is typing the Relations collection as follows:

 foreach (IEntityRelation relation in filter.Relations)
{
    if (relation.AliasRightOperand.Equals("Siteaddress"))
    {
        relation.CustomFilter = new PredicateExpression(SiteaddressFields.Idtypeofaddress.SetObjectAlias("Siteaddress") == typeOfAddressID);
        break;
    }
}

Does this jibe with the approach you took?  And if not, how'd you get that v2.5 code to work in v2.6?

William wrote:

Does this jibe with the approach you took? And if not, how'd you get that v2.5 code to work in v2.6?

Yes that's it! I used _IRelation _interface in both v2.5 and v2.6.

Ah, that was the reason I couldn't get it working in v2.5.

Thanks for the help!