I come across instances very often with clients, where they want to group some data by a field on a page type and display a @jump to@ menu at the top, and then group the item display on the page by that field.For example:Posts2016 | 2015 | 2014 | 20132016Post 1Post 2Post 32015Post 4Post 5Post 6Et cetera.I've done a lot of reading on Kentico's documentation, and nothing really points me to what I want, which is a clean way to achieve this just by configuring one or more web parts in the portal engine - no custom code, no inline ASP code or controls.I just want a one (two?)-level hierarchy - a web part where I can say @From this place in the document tree, for this page type, group by this field, and use this transformation for the parent level and this transformation for the child level.@ I don't want a @Hierarchical@ structure with infinite parents/children, I want exactly one parent/child level - a @GROUP BY@ equivalent, if you will.In the scenario above, I would need two of these web parts - one to display the anchor links at the top, and the other to display the full headers and links underneath them.Is this even remotely possible? Typically with solutions like these, I will just turn to JavaScript (and output the page fields to JSON), but I really don't like doing things that way. I just don't understand why this is so difficult with Kentico. I struggle with this all the time - so much so that I'm considering writing my own web part to accomplish this - though I'd rather not!Any insights?
↧