Forum Discussion
Very disappointed in the Highlighted Content web part
I tried that one a while ago and couldn’t get it to install. Anyway, the HC web part has a number of bugs in it that I would imagine would frustrate its intended audience, no matter how amateur they might be.
https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration?category_id=203542
- Fleur WilliamsonOct 14, 2019Copper Contributor
I have to agree with the OP. This Webpart does not always perform as expected. I am trying to filter pages based on Page Properties, and it just doesn't let me select any properties. This is surely a bug and I don't think it is an unrealistic expectation to not have bugs.
- Jenny BruceOct 16, 2019Iron Contributor
I was also formerly critical of Highlighted Content web part, but it is improving.
You need to make sure any custom properties (column names) you've created are included in the search index and/or it needs to be a 'managed property'. If you're not a SharePoint Admin, ask yours to check this. This doesn't happen automatically in SharePoint Online Modern.
Once your custom properties are being crawled, they should show up when you change the Filter to 'Managed property', then type part of the string from your column label into the 'enter search words' field (I don't put in the full string as you need to remember to include _x0020_ if you have spaces in your column names - a partial string will usually be enough to find your property), then select from the options that become available in the 'Managed property drop down' below the search field.
If you are just trying to use Highlighted Content web part for documents in a document library, change the source to 'A document library on this site', then you'll get a 'Column name' option in the filters rather than 'managed property'.
- Brandon MurrayOct 27, 2018Brass Contributor
Well, I respectfully disagree... "no bugs" at least is not an expectation too high. And I think it's also completely reasonable to expect not just similar but better capabilities when a customer goes through the large hassle of upgrading the user interface. If someone wants to use the Modern UI--and I do!--they shouldn't be forced to use an inferior set of web parts. I know that MS is developing in an iterative pace nowadays, but these sites are now production, and the HC web part has been out for years.
We need a faster cadence on the most important capabilities that are still missing in the Modern UI.
The promise of SharePoint used to be that a power user with little or no development background could still use SharePoint to make amazing things. I don't see that being the reality yet in the Modern UI, forcing many to continue to build sites on the more robust Classic UI.
- Ali SalihOct 27, 2018Iron Contributor
I do not entirely disagree with you. However, the current version of HCWP is what the current version is, and *you* are making the decision to move to Modern UI, you are not immediately forced to make a such move. So since it is not meeting your requirements, you are calling it almost a lemon. That's the part I was mentioning about setting expectations too high. "Real Bugs" -> If the HCWP is supposed to do something and you select it, and it doesn't do that particular function, or errors out, sure Report them. Some of the stuff you mention is something I've not directly experienced, so I can't comment if they are bugs or missing features.
Your point about being forced to use Classical UI due to features missing is something 100% I agree with as a concern and it should have been a more significant concern when Modern UI was being rolled out, that said it is entirely valid to ask the question of why hold back a very nice improvement that will immediately bring value to to *most* customers, while it is getting better and better to improve *all* customer experiences. my $0.02
- Jenny BruceNov 21, 2018Iron Contributor
Sorry Ali, but I agree with Brandon.
The HCWP is extremely disappointing when compared with how robust and flexible the old CQWP was.
I had no choice about going to Modern. Our local Microsoft reps came in all 'jazz hands' and told my decision makers to rebuild our intranet using Modern.
If HCWP is intended for novice users, fine, but Microsoft also needs to have a CQWP equivalent for users who do understand how to use it to build more complex queries.
- John WynneOct 27, 2018Silver ContributorHi Brandon, I'm looping in Mark-Kashman and Chris McNulty in for their views on the issues you raise. They in turn can loop in other Microsoft colleagues to hopefully address some of the problems you are experiencing.