Below are a few questions and answers that will help you determine could you use ToolZ for your needs, and what you can expect. If any of the articles are non-negotiable, you will most likely not find ToolZ to be what you require.


You can also check the capabilities of ToolZ in another help article.


Does the data need to be updated in real-time?

If the data absolutely needs to be updated the instant it changes in SASSIE, the report cannot be done in ToolZ.


The most often ToolZ data can update is daily.


Does the report need to work for all clients/surveys?

If the report absolutely has to be useable for all of their clients and surveys, then it cannot be done in ToolZ.


Reports can easily be copied and modified for additional clients and surveys, but it’s not feasible to do this for all clients and surveys.


Does the report include data that is not exported to ToolZ?

The data we currently export is listed here. If it’s not on this list, it’s not exported, and the report is probably not doable with ToolZ.


However, you may be able to use RuleZ or a customization can be used to fill the data into a question type that is exported.


Does the report need to match Sassie's controls exactly?

If the client really cannot tolerate having report controls that operate differently from Sassie's controls, then the report cannot be done with ToolZ.


For the most part, ToolZ is capable of filtering data the same way that Sassie is, but the control setup is slightly different.


Does the report need to show a ton of data at once?

A report that needs to display a lot of data all at once (no pagination) is probably best not done in ToolZ.


ToolZ has limits on how much data it can display before reaching memory and timeout limits. Unfortunately, these limits aren’t well-defined, but hundreds of questions and/or thousands of shops will probably result in timeouts.


Does the report’s layout need to be configured by the end user?

If the report has controls that determine the structure of the report, it should not be done in ToolZ.


Examples of this include: multiple dynamically-selected date ranges, selecting which question/section to report on, selecting which level type to report on, or switching between different report layouts. ToolZ is aimed at creating highly-customized, relatively static reports. Reports that are essentially mini report-builders are best done fully custom.


Does the report have a complex dynamic layout?

If the report has to dynamically arrange its data in a complex manner, it should not be done in ToolZ.


This is especially true if the report needs to make associations between data that has no actual association, such as several questions “belonging” to a larger conceptual grouping.