Hi George,

It seems this is a bug in our WebCombo which WebCombo could not recognize an alias. I have submitted this to our developer. They are checking it right now and i will let you know the result.

Regards,
Handy

Handy

Please have them check the use of a stored procedure, too.

George

for the sample use the Ten Most Expensive products stored procedure that is in NorthWind. I don't know if i have the name correct but it is easy to find.

Ok, I have forwarded this to our developer. Thank you.

Hi George,

After analyzing your issue further, we found that the issue is not a bug in WebCombo. It's more to the LINQ limitation in which new select projection will cause underlying datasource's schema to be invalid. This caused WebCombo to unable to filter the "conditions" clause because the target members are no longer existed in the datasource after the new projection.

Unlike WebGrid which processes all data after data retrieval, WebCombo requires pre-databound filtering process. As such, WebCombo requires the fields used in DataTextField and DataValueField to remain the same after the new projection.

The following code shows the working version of WebCombo bound to LINQ DataSource.

<ISWebCombo:WebCombo ID="WebCombo1" runat="server" 
        DataSourceID="ISLinqDataSource1" DataTextField="ProductName" 
        DataValueField="ProductName" Height="20px" 
        UseDefaultStyle="True" 
        Width="200px">
    </ISWebCombo:WebCombo>
    <ISLinqDataSource:ISLinqDataSource ID="ISLinqDataSource1" runat="server" 
        ContextTypeName="NorthwindDataContext" 
        Select="new (ProductName, UnitPrice)" 
        TableName="Products">
    </ISLinqDataSource:ISLinqDataSource>

Let me know if you have any questions. 

Hope this helps.