If a report is taking a long time to load before prompting the User for values, it may be trying to pull information in from too many different places. Here's where to look first:

  • The report is retrieving data from a "xxx 2014.x" Universe. These Universes are frozen, any changes to the underlying forms will not be reflected and the customer should migrate to a Custom Universe.

  • If a single Query is retrieving data from a number of different types of sources (demographics, assessments, Points of Service, TouchPoints, Caseload, family data, etc.) this can affect speed. It is recommended to split the Query.

  • Points of Service and Assessment should always have a Query on their own, and should include only Identity data.

  • If a report contains multiple Queries and is running slowly, you can add a "Query status" report to see which ones are taking a long time to refresh.

  • Using the "Active Filter" in a Query can sometimes slow a report down.

  • Do not include more than four TouchPoints in a single Query, this can slow a report down.

  • Using Combination Queries (Union, Intersect and minus) can slow a report down.


See also: ETO Results: Running a Query Status Report

Did this answer your question?