Best practice for scheduling Perceive's Report Events

This article will outline the best practice for creating and configuring Infogix Perceive Report Events in a way to mitigate blank or erroneous reports.

When creating a Report Event, it will have a trigger based upon the output of an Extract Event. Extract Events often have multiple outputs though, such as the reference Extract Event below:

When selecting the trigger criteria, the last output in the Extract Event should be chosen. For the Extract Event shown above, the best output to select within the Report Event's trigger is the "User Report ..." output: 

If this Report Event uses the “control data” as the trigger, which is the first extract listed, and the report relies in data from any of the subsequent extracts, the report will execute and before the rest of the data is loaded, leading to blank or erroneous reports. By selecting the final Extract Event output, the report won't trigger until all of the data in the Extract Event is extracted.