I created a document type called fact sheet, it has location and general information about company facilities, it doesn't inherit anything from any other types.

Because of the way they want the list of fact sheet locations to be displayed(all of the information is associated with one document type, they just have the listing page displaying location information), I am using a custom query ti retrieve all of the relevant data including some information being joined to from a couple of other tables. I was going to use a nested repeater and just reference the fact sheets using the path setting, but the additional information made that unruly.

So my plan was to have parent pages(in this case geographic regions) and then just place the relevant fact sheet locations under each parent, setting the where clause to filter the data being returned via my query. So the tree looks like this

North America
Fact Sheet 1
Fact Sheet 2
Asia
Fact Sheet 1
Fact Sheet 2

Region being an attribute of my fact sheet document type. So in the past I have used a simple repeater with a default and preview transformation for new items, and I had hoped to set something like that up for this. However I do not think that is possible since I am using a query as opposed to a path to generate my list of fact sheets and do not seem to have access to any actual document information, like node ID, document url, etc.

So I am wondering if I can add that information to my query or if I am just not calling it correctly. Does that make sense?