Find a post...

DNN-Connect Blogs

New in 2sxc 7: #2 Using Visual Query with Token Templates

This is a part of my series The New Features of 2sxc 7 and introduces you to the Token-Repeat enhancements and how to use them together with the Visual Query

There are many common ways to consume Query data - the simplest one is to use tokens. 

Note that it's easiest to learn this by using the App I prepared for you containing all these examples. The output can be seen here, the App can be downloaded here

Configure a Template to use a Query

To tell a template that it must use a predefined Query instead of the normal content-items, you must configure it in the template settings here:

If you do this, then all data-streams delivered by the query can be used in the template - using the new repeater-syntax. In 2sxc 6 there were only a few token sources available like Content, ListContent, QueryString, App and DNN-sources like Tab, Portal etc. and there was no need to repeat any other list - because there was only a content-list. So repeating was made possible through a simple <repeat> tag. 

But to be able to loop through a query with multiple streams like this:

...we had to extend the repeat which allowed you to repeat across any stream you wanted to. So we introduced the new syntax:

<repeat repeat="InnerTokenName in Data:StreamName">



For a realistic example, this could look like this: 


    <repeat repeat="Feedb in Data:Feedback">




This is very simple and easy to understand - but together with the Visual Query Designer (see this post) this allows you to create pretty cool tools, and with the new View-Name-In-URL (wait for that post) this allows you to create very complex list-details scenarios without any code at all. 

A Note on Using List-Iterators

The token engine automatically provides you with additional list-information on this iterator. The syntax is 

- where specialkey can be things like Index, Index1, Count, Alternator, IsFirst...


    <repeat repeat="Feedb in Data:Feedback">

        <li> - this is Feedback of </li>



A Note on Using Presentation Information

2sxc offers a special feature called Presentation. This is a page/module-specific additional information on how a content-item (like an address) is to be displayed on this specific page/module. When using it without Queries, you would write

...or something similar. But now that we have queries, how can we use this? The answer is simple, but requires a bit of background knowledge:

  1. Presentation is only available for content which was really added to a specific module - because only module-specific-content has presentation information. This is because an address can have different presentation-settings in each use-case. 
  2. So if you retrieve a list of all addresses in an App, you will not have any specific Presentation
  3. But if you retrieve the Addresses of a specific module, it will have presentation (assuming that the template actually uses presentation). 

In summary - only the Default-Stream and the ListContent-Stream from the ModuleDataSource can have a presentation-property (but doesn't always have one, this depends on the template settings), all other streams don't. 

Using that would look as follows:





    <repeat repeat="Address in Data:Default">

        <li class="></li>



The template above first creates a h1/h2/h3 etc. tag (based on the ListContent-Presentation configuration) and places the title into that, then it creates a list which is colored by the settin in the Address-Presentation (and defaults to "color-default") if nothing is set, then shows the City. 

A note on Query-Parameters with Token-Templates

Since a Query can contain any kind of parameters like or 97 or even these are automatically resolved by the Query-Engine whenever you access the query. You don't have to do anything - it just works. 

With love from Switzerland,


Daniel Mettler grew up in the jungles of Indonesia and is founder and CEO of 2sic internet solutions in Switzerland and Liechtenstein, an 20-head web specialist with over 600 DNN projects since 1999. He is also chief architect of 2sxc (2SexyContent - see forge), an open source module for creating attractive content and DNN Apps.

Daniel Mettler learned programming with the bible translation computer of his parents, deep in the jungles of Indonesia. Since he was only 12 years old at that time and the BIOS only had a version of BASICA, that's what got him started. With 16 he went back to Switzerland and learned German and basic city-survival skills. Equipped with this know-how he founded 2sic internet solutions in 1999 which was focused on web solutions on the Microsoft platform. After a few self-developed CMSs 2sic switched to DNN in 2003 and has been one of the largest partners (17 employees, 700+ projects) in Europe. Daniel is also the chief architect behind the open source 2sxc, a strong promoter of standardization (boostrap, patterns, AngularJS, checklists, etc.) and loves to eat anything - dead or alive. His motto: if the natives eat it, it game.
Phil Speth
  The sample link is not working. Just fyi This looks like an exciting example. I will be digging into it this week. THX
· reply · 0 0 0

Hosting liberally provided by

Philipp Becker 6011 7
Geoff Barlow 542 4
DNN-Connect 431 6
Peter Donker 5092 30
Christopher Hammond 683 2
Olivier Jooris 418 1
Daniel Mettler 12054 88
Clint Patterson 1 1
Jos Richters 65 1
James Rosewell 327 2
Will Strohl 1550 27
Ernst Peter Tamminga 438 4
Barry Waluszko 2802 2
Declan Ward 468 1
Gifford Watkins 722 9
Torsten Weggen 2796 3