Lazy loaded property value is not supported exception

London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

AI OnAI Off

Home / Forums / Developers (Main Products) Forum / CMS 7.5 - 11 /

Lazy loaded property value is not supported exception

Carl S

Vote:

Hi. When loading a page instance trough FindPagesWithCritieria (PageTypeID) this weird error occurs.

Lazy loaded property value is not supported by the current property instance
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: Lazy loaded property value is not supported by the current property instance

Source Error:


Line 138:                }
Line 139:            };
Line 140:            return DataFactory.Instance
Line 141:                .FindPagesWithCriteria(contentLink.ToPageReference(),criteriaCollection)
Line 142:                .OfType<T>().ToList();

As far as I know we only have virtual properties on this page type. Any idea why this is happening?

We load a similar page type on another site and it works perfectly.

It seems related to the site somehow, "develop" and "master" branch has the same exception.

#228500

Sep 28, 2020 5:50

Carl S

Vote:

This exception seems to break Epi backoffice as well. Get exception in loading children to the start page of the site.

#228502

Sep 28, 2020 6:04

Carl S - Sep 28, 2020 6:09

Note. Changing database to a production copy does not resolve the issue. We do NOT want this error propagated to production.

Carl S

Vote:

Ok this seems to be releated to custom properties we have added to a different branch. So strange that Epi can't handle this.

Soft warning instead of exception.

#228504

Sep 28, 2020 6:18

This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.