On the UI side, Nic Galler has this kind of construct:

<pre>
<LookupPreFilters>
<SalesLogix:LookupPreFilter PropertyName=”Id” CondOperator=”Not Equal to”
FilterValue=”‘xxx’ and Id in (select sr.User.Id from OwnerRights sr where sr.Owner.OwnerDescription=’Lit Fulfillment&rsquo and Id not in (select u.Id from User u where u.Type=’R')” />
</LookupPreFilters>
</pre>

This is the same kind of trick we used in the LAN side to use an IN clause to allow the ORing of conditions to a Lookup Control.

So on the code behind ascx.cs this would be something like (per Mark Dykun):

        dplArea.LookupPreFilters.Clear();
        if (!IsInTeam(CurrentUser, "SIG Private"))
        {
            LookupPreFilter filter = new LookupPreFilter("Area", "E-Adjustment" , CondOperator = "!=" );
            dplArea.LookupPreFilters.Add(filter);
            dplArea.InvalidateControlCache();
        }
And you would have the IN clause buried in your condition operator.....same as in the LAN client.
Am still (as of this) trying to figure out the LookupPreFilter(s) object.

ok

I've tried

<SalesLogix:LookupPreFilter PropertyName="Type" PropertyType="System.String" OperatorCode="="
FilterValue="'Partner' and Subtype in ('Reseller', 'OEM Headquarter', 'OEM Subsidery')">
</SalesLogix:LookupPreFilter>

and it dosen't work. Any hints?

kind regards

Do you have a link to Nic Gallers post? I can't find it.

I think the original post was from 2009, long before InvalidateControlCache(); existed.

Hi,

I understand  the possibility on the code side. It's interesting for me how to set up these filters on the UI side because it's better for maintenance.

Any ideas?

Jörn

ok here is the link to the blog

http://blog.nicocrm.com/2009/05/15/tips-tricks-of-the-web-client/