Hi all,

Im grabbing entities from a table and applying a filter so that I do not get all of the results.

EntityCollection directoryCollection = new  EntityCollection(new DirectoryEntityFactory());
RelationPredicateBucket A = new RelationPredicateBucket();
                A.PredicateExpression.Add(PredicateFactory.CompareValue( TotalIngenuity.Module.Directory.DAL.DirectoryFieldIndex.PortalID,ComparisonOperator.Equal,0));
            A.PredicateExpression.AddWithAnd(PredicateFactory.CompareValue( TotalIngenuity.Module.Directory.DAL.DirectoryFieldIndex.Type,ComparisonOperator.Equal,true));

DataAccessAdapter adapterForDirectory = new DataAccessAdapter();
adapterForDirectory.FetchEntityCollection(directoryCollection, A);

This should fill directoryCollection with all the relevant directory entries but it throws an error.

Anyone know what I'm doing wrong?

Thanks,

John

which error does it throw?

btw, I think it uses the wrong overload or it can't choose between which overload to use. If you specify a boolean as a value, first specify false for the negate. (thus use the overload which accepts the boolean negate)

Otis wrote:

which error does it throw?

btw, I think it uses the wrong overload or it can't choose between which overload to use. If you specify a boolean as a value, first specify false for the negate. (thus use the overload which accepts the boolean negate)

Hi Frans.

It wasn't a problem with the code but with the deployment of the dlls. Sorry for the unnecessary querstion.

But thanks for the quick response.

With your comment on the use of boolean could you give an example of what you mean?

Many thanks,

John

No, that was just me looking at your code and messing things up

What I thought was: calling CompareValue() by specifying 'true' as the value would cause problems with the overload which also accepts a value for negate (boolean). But I was assuming that the value to compare with was optional (as it is in the FieldCompareValuePredicate() object, which is called by the PredicateFactory) however this isn't the case . I was confusing the two.

Otis wrote:

No, that was just me looking at your code and messing things up

What I thought was: calling CompareValue() by specifying 'true' as the value would cause problems with the overload which also accepts a value for negate (boolean). But I was assuming that the value to compare with was optional (as it is in the FieldCompareValuePredicate() object, which is called by the PredicateFactory) however this isn't the case . I was confusing the two.

Thanks for your quick responses either way

Rainbow wrote:

Thanks for your quick responses either way

Btw, is Rainbow v2 using an LLBLGen Pro core or is it used for prototyping? (just curious , you may answer by email, people working on dotnetnuke are reading here too )

Otis wrote:

Btw, is Rainbow v2 using an LLBLGen Pro core or is it used for prototyping? (just curious , you may answer by email, people working on dotnetnuke are reading here too )

who me?

Rainbow using LLBLGen core ... interesting..... I know LLBLGen.... I guess I just need to polish up on my C#

bert