SOCKETWorx satisfies database reporting requirements by producing Excel workbooks from Views.  In many use cases, the output is producing deliverables such as Lists, or Reports.


One must consider the old adage of 'what came first, the chicken or the egg?'.   Relative to SOCKETWorx Views should be established first.  Report Templates are orphans without an associated Views.  So, Views must come before Reports Templates.


Another setup consideration is whether to use the View grid header values in Reports.  


SOCKETWorx always populates these grid headers with the Table Field Display Names.  Users have complete control to enter these values under the Setup>Table>Fields utilities.  These User friendly Display Names can service both View and their Reports.  It's easy to service the Reports,  just check the 'Include Headers' option when creating a Report Template.


It all really boils down to using the Field Display Names in reports or not.

If not, then Users must setup alternative headers within the Report Templates using the Report Template Editor.  

In some situation taking control of column headers in the Report Templates just make sense.

Just be aware there are options.


This article explores both these setup and configuration scenarios and is intended to provide some strategic ideas on how to go about setting up, configuring and otherwise managing Report Templates within SOCKETWorx.


Again, the Chick or the Egg Question?

It is important to realize that Users can only associate, or assign, Report Templates to Views if they exists.  

So it doesn't make much sense to build Report Templates unless you have corresponding Views created first.  


Furthermore, when adding a new Report Template it is not possible to assign a View to it because the Report Template being added has yet to be establish in the system.  So, Users must 1) Add a new Report Template and then 2) Edit it to associate a View.



User need to be aware that Report Templates can be associated to Views via a couple methods.  Also, it is important to know that each method has an impact on a Report Template utilization.    


How Report Templates are associated to View makes a difference!

Lock it Up

So above we see how Users can associate Views to Report Templates using the Modify Report Template Modify button.


When using this method, The Report Template is 'Locked' to the View which means it can not be applied to any other Views.

Also, if you Edit the associated View you'll see that the Report Template selection is disabled and there is a green circle with a check mark indicating that that association is locked within the Report Template Setup.  No changes can be made while Editing a View once a Report Template is assigned using this method.



Keep it Global

If a Report Template is going to be applicable to multiple views, then Users should associated them as part of the View setup an configuration.  When Report Templates are consumed this way, multiple Views can use the same Report Template.