Ambiguous match found

[Yang]

I am using a customised linq to sql datacontext in a objectdatasource. When I add this datasource to a table, it shows error  'Ambiguous match found'. I think it's my Shadowed property that causes this error. Is there any work around? I need to use Shadows as I want to hide the property generated from  linq to sql datacontext and use my inherited class with pre-filtering.

This is what my customised datacontext looks like: 

Public Class ReportTestFiltered
  Inherits ReportTestDataContext
  Public Sub New()
    MyBase.New()
  End Sub

  Public Shadows ReadOnly Property Users() As IQueryable(Of User)
    Get
      Return MyBase.Users.Where(Function(x) x.Active).AsQueryable()
    End Get
  End Property
End Class

[KS]

Hi,

Check this - http://stackoverflow.com/questions/13032395/ambiguous-match-found
Still check if the data schema for User can be retrieved this way.

-KS

[Yang]

That would work if I had the source code of object datasource. I haven't found a workaround it yet. 

[IvanY]

Hello Yang Qu,

You should not be using shadow properties. In theory you can get with reflection all the properties with the same name. However there is no easy way to specify which property from which class you should be using. Therefore such scenario is not supported.

As a workaround you can create wrapper class that takes the information from your class. Then just use the wrapper class for your reports instead of the original class that has shadowed properties.

Regards,
IvanY
Telerik