Universal Hierarchy Viewer with Custom Table Data

Hi,

So which Web Part are you using? You mention

• Universal Hierarchy Viewer with Custom Table Data
• universal viewer with custom data

But those don't exist...

I tried doing as much as what you described and when I use the following I get working data:

Web Part: Universal Viewer With Custom Query properties:

• ID column: ItemID
• ParentID Column: ParentID
• Level column: Level
• Load hierarchical data: checked
• Use default hierarchical order: checked

Query:

SELECT 1 AS ItemID, NULL as ParentID, 0 as Level, 'Default' as [FolderName], null as DocumentName
UNION
SELECT 2 as ItemID, 1 AS ParentID, 1 as Level, null, 'File' as [DocumentName]
ORDER BY ##ORDERBY##

Hierarchical transformation:

Transformation (text/XML): (I've set both the same for demostration)

<p>
 ItemID - {%ItemID%};
 ParentID - {%ParentID%};
 Level - {%Level%};
 Folder - {%FolderName%};
 Document - {%DocumentName%};
<p>

Result

Keep in mind if you are using the "class" feature of hierarchy transformation, you should adjust your custom query to also return as "classname" column with the right code name, you also seem to be missing the nodeorder field which you also need. You can use the row() over (partition by x order by y) type of SQL logic

Thank you for the answers. Yes, I am using the Universal Viewer with Custom Query, I just wanted to stress that I wasn't pulling in page data, but custom data.

Do you know if the Hierarchy functions of that viewer require jQuery?

I know you aren't pulling page data, however how the hierarchy transformations work is it takes the NodeLevel, NodeOrder, ItemID, ParentID, and the "ClassName" of the current row and matches it with the transformation that applies (if no Class Name, then only "All" typed transformations will be applied).

If page type is set to "All" in your hierarchy transformation item then you're fine, just wanted to specify in case you set a page type (say CMS.Folder) on the hierarchy transformation, then your query must return a column "ClassName" and the value of "CMS.Folder" for that transformation to kick in.

Anyway, based on what you have, you probably just have the Universal Viewer misconfigured, or it's complaining because you are missing an Order field (but probably not), can you screenshot the settings you have for the hierarchy viewer? And one of the Hierarchy Transformation you're using?

Thank you both for the answers. I tried my code on another installation that I use to test and it worked as expected. I think somehow our javascript/jQuery isn't firing, and even if it isn't directly affecting the universal viewer, it might be indirectly.

Thank you again. This is a big help.