Field 'Library' not found on class 'Telerik.Site

Hi,

The following line of code:

Hi Thomas,

I'm sorry to hear about the issues you are experiencing querying Documents. I have tested the sample you provided, but it's working fine locally, provided that I specify a valid UrlName (default-document-library in my case). Further, checking with our codebase, shows that objects of type Telerik.Sitefinity.Libraries.Model.Document do have a property Library declared (should be the same as using d.Parent) so there should be no problem using it as a filter in the lambda expression for filtering documents. Can you please share with us if there's anything else that you might consider helpful in letting us find out the reasons behind the problems you are experiencing? Thank you in advance!

Regards,
Boyan Barnev
the Telerik team

Hi Boyan,

"Telerik.Sitefinity.Libraries.Model.Document do have a property Library declared (should be the same as using d.Parent) so there should be no problem using it as a filter in the lambda expression for filtering documents."

Yes, of course. That's why my code actually compiles, but fails during execution.
I'm not sure what else I could tell you to help you debug this. My UrlName is also valid, for a specific (non-default) library. I just tried with the default library, and it's the same.

A colleague just told me he tried to do the same thing before, and that it didn't work for him either. So we both ended up going for a foreach loop instead.

Are you testing this from 4.2, or maybe from a more recent internal build? That's all I can think of.

Hi Thomas,

Thank you for getting back to me. Yes, I'm testing on our latest officially supported release (4.2 Hotfix 1) and also on the latest internal codebase, can you please try using Parent instead of Library and let me know if the issues persist. Also, is the problem project-specific, or it reproduces on a new project as well?

All the best,
Boyan Barnev
the Telerik team

Hi Boyan,

It actually works with Parent!
Tried again with Library, and it still doesn't work.

Is using Parent recommended / future proof? Is it guaranteed not to break with future Sitefinity versions?

I don't have the time to try with a new project, sorry. Maybe in a few weeks, if it's really useful to you.
On the other hand, I managed to get a slightly different exception (using the Library property), which may be useful to you:

Hi Thomas,

That's a really peculiar behavior, I'm really curious if it will reproduce with an empty project on your side, please do not hesitate to let me know if you have had the time to test it. Generally, using Parent in the filter expression is safe, yes. Actually the Library property is a return of the parent, cast to DocumentLibrary type.  ((DocumentLibrary)this.Parent; )

Regards,
Boyan Barnev
the Telerik team

I have the same issue when executing this code:

Hello Daniel,

The possible cause for the problems experienced is if you're using the "Library" property in a lambda expression. The reason for the problems is that the persisted field is Parent, while Library is a property that is internally retrieved as (<T>)this.Parent;  and when you're operating with an IQueryable  the Library property is not available unless you have made a ToList() call beforehand. What I'd recommend you as the correct approach is to use Parent. One more thing that's worth noting is that Parent.Title is an LString, so if you're passing the Library title in your query, you'd better cast it ToString().

All the best,
Boyan Barnev
the Telerik team

Hi Boyan,

Thanks for the explanation for this issue. But then, I'm confused why the sample I provided worked at all for you, as you said in your first reply. It shouldn't have, from what you just explained.

Hello Thomas,

Thank you for pointing this out, I'll need to research whether there might have been some internal ToList() call in the previous versions that could have made this possible, or whether I have not made that call unintentionally.

Regards,
Boyan Barnev
the Telerik team