LINQ to Entities does not recognize the method "System.Object GetValue(System.Object, System.Object[])

[netnr]

ERROR：LINQ to Entities 不识别方法“System.Object GetValue(System.Object, System.Object[])”，因此该方法无法转换为存储表达式。

This way can be in ef core 2.1

query.Where(x => EF.Functions.Like(x.GetType().GetProperty("field").GetValue(x, null).ToString(), "%12%")

Further technical details

EF version: (EntityFramework 6.2.0)
Database Provider: (e.g. EntityFramework.SqlServer)
Operating system: (e.g. Windows 10)
IDE: (e.g. Visual Studio 2017 15.6)

[ajcvickers]

EF Team Triage: This issue is lacking enough information for us to be able to effectively triage it. In particular, it is missing the following information requested in the new issue template. Can you please provide this information?

Steps to reproduce

Ideally include a complete code listing that we can run to reproduce the issue.
Alternatively, you can provide a project/solution that we can run.

BTW we're not just doing this to be mean 😄... we get a lot traffic on this project and it takes time to attempt to reproduce an issue based on fragments of information. In addition, our attempt is often unsuccessful as the exact conditions required to hit the issue are often not explicitly included in the code provided. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we ask that folks give us a self-contained way to reproduce an issue.

For a guide on submitting good bug reports, read Painless Bug Tracking.

BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.

[ajcvickers]

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.

BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.