Strange Exception thrown using Dynamic Linq Entity Framework Query

Question

I have a gallery entity framework class,and I'm attempting to use the Dynamic Linq Library posted on ScottGu's blog to query the entity set. The failing line of code reads:

return context.Galleries.OrderBy(sidx + " " + sord).Skip(page * rows).Take(rows).ToList();

sidx=="Name", and sord=="desc".

The Gallery object does have a property called "Name". However, when executed, i get the following exception:

'Title' could not be resolved in the current scope or context. Make sure that all referenced variables are in scope, that required schemas are loaded, and that namespaces are referenced correctly., near simple identifier, line 6, column 1.

Does anyone know what this means?

The bug is somewhere else, probably in the query. The line of code you include is simply the line which executes the query (because of the ToList). You see the error surface there, but the real bug is elsewhere. My first guess would be the mapping, but there's not nearly enough code here to tell. — Craig Stuntz, Jul 27 '09 at 19:56

score 8 · Answer 1 · answered Mar 06 '12 at 08:49

8

"it" alias was the problem so the following code should works:

prefix your filter field name Title as it.Title

I found the answer here .. http://challenge-me.ws/?tag=/Exceptions

answered Mar 06 '12 at 08:49

Thant Zin

543
5
8

Had the same message as OP and this was the fix. – Andrew Boes Mar 28 '12 at 22:21
Doh! Was looking 2 days for a fix. Thanks for that! – Oliver Kötter Jun 19 '12 at 15:25

score 2 · Answer 2 · answered Sep 21 '11 at 16:13

2

use: AsQueryable<>

return context.Galleries.AsQueryable().OrderBy(sidx + " " + sord).Skip(page * rows).Take(rows).ToList();

answered Sep 21 '11 at 16:13

Behruz Tolibov

455
4
7

score 0 · Accepted Answer · answered Jul 28 '09 at 01:43

I found a fix, but it doesnt explain the original issue. The query was in a library, and being referenced from the asp.net mvc application. It compiled fine, but bombed at runtime. The fix was putting the dynamiclinq class in the mvc app itself, returning a plain IQueryable form the library, and doing the filtering in the controller itself. The exact same code worked there. Somehow the separation in the library caused the issue.

Strange Exception thrown using Dynamic Linq Entity Framework Query

3 Answers3

Linked