Forum Discussion
Page properties not visible for filtering news webpart
- Jul 25, 2019
stevenam Can you see that each column is associated to the content types in library settings? I would try on a new site and see if the issue is the site itself. I was not able to filter on Yes/No columns in the News web part, but I use choice columns all the time and they work.
Has anyone tried to use a lookup column within the Page Properties web part? I've been wrestling with a similar issue to this myself. I've found that for me I either need to unseal the Site Page content type to reveal extra filter choices within the page properties web part, or it only affects older sites (possibly pre-September 2019 as described https://sharepoint.stackexchange.com/questions/252495/why-site-page-content-type-is-missing-the-options-under-its-settings-section).
So as Susan and others have said, creating new sites seems to rectify the issue for most, but I'm using lookup columns as my library form has dependant drop-downs and the columns won't show is the page properties webpart. Is there a list of supported field types or anything?
Cheers,
Anthony
- Steph_AusAug 24, 2021Copper Contributor
anthony tudor Did you find a solution to the problem of Lookup columns not being supported in the News webpart filter? I have looked all over the place and i could only find that Lookup columns in the Site Pages Library is supposed to be a supported page property. However i have tested on two different Teams sites that if i create a lookup column that is won't show up in the page properties filter for the News webpart. It is really frustrating because i also can't dynamically filter the news webpart either.
- amira198715Nov 17, 2022Copper Contributor
Steph_Aus hello , did you find a solution for your lookup field on the web part , i'm facing the some issue
- Steph_AusNov 17, 2022Copper Contributor
amira198715 No I didn't find a solution. I just ended up changing the fields so they weren't lookups, rather just standard list fields. I haven't tried it since to see if things have been updated to fix this, though i am guessing if you are also having the problem then it hasn't been fixed.