Per Nergård
Apr 8, 2010
(0 votes)

FilterRemoveNullValues change in CMS 5

In CMS 4 for the filter to remove a page the property specified  had to exist on the page being filtered as well as the value being null.

In CMS 5 this has changed so the filter always assumes that the property always exist and only checks if the property value is null.

I guess that’s not wrong but depending on the circumstances I can see a possibility that you have a mixed page data collection from different sources where you just want to do the filtering on only the pages that have this particular property and just ignore the rest.

In my case we hade some old code that used this filter and still returned pages due to the property exist check. But after migrating to CMS 5 all pages got filtered out.

Apr 08, 2010


Please login to comment.
Latest blogs
Optimizely community meetup - Sept 29 (virtual + Melbourne)

Super excited to be presenting this Thursday the 29th of September at the Optimizely community meetup. For the full details and RSVP's see the...

Ynze | Sep 27, 2022 | Syndicated blog

Preview multiple Visitor Groups directly while browsing your Optimizely site

Visitor groups are great - it's an easy way to add personalization towards market segments to your site. But it does come with it's own set of...

Allan Thraen | Sep 26, 2022 | Syndicated blog

The Report Center is finally back in Optimizely CMS 12

With Episerver.CMS.UI 12.12.0 the Report Center is finally re-introduced in the core product.

Tomas Hensrud Gulla | Sep 26, 2022 | Syndicated blog

Dynamic Route in ASP.NET Core When MapDynamicControllerRoute Does Not Work

Background Creating one of the add-on for Optimizely I had to deal with challenge to register dynamically route for the API controller. Dynamic rou...

valdis | Sep 25, 2022 | Syndicated blog