logo

Warning: The forum is now for consultation only. Please use GitHub Discussions to post any questions or comments.


Welcome Guest ! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
epf  
#1 Posted : Monday, March 3, 2014 4:38:23 PM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 1,209
Switzerland

Thanks: 14 times
Was thanked: 205 time(s) in 198 post(s)
Actually when you edit a report and you create a new Data Source, you will notice that a default table is always inserted in the Source.
This table called SealMasterTable table is dynamic: this means that its columns are built from the Select SQL Statement that you have defined.

This table is mainly used if you have a custom SQL Select statement that cannot be built automatically from the other tables.
Just enter the SQL Statement as part of the definition of the SealMaster table and you can then use the columns/elements defined in your models.

As SealMasterTable is a normal table, you may also defined Joins to connect to the other tables and to use also the elements from the other tables in your models.
This is a quite powerful feature as you have the flexibility of using you custom SQL and to use also all the tables of your repository.

Note that SealMasterTable is just a static hardcoded name, you can add other Dynamic tables with other names without problems.
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.