Decouple Data Export Temporal Filter from Dashboard Settings

In IBM Envizi, the ‘Dataset Maximum Time period’ setting creates a conflict by controlling two separate functions: the front-end dashboard's temporal slicer and the data available via the Data Export function. There is an inherent tension between optimizing the front-end user experience and ensuring complete data availability via the Data Export function, as the expectation is that all data should be available through the Data Export function.

This leads to several critical issues:

• Data Incompleteness: The function has a 10-year maximum, which creates data completeness problems for clients with more than ten years of data
• Negative User Experience: Setting the filter to 10 years negatively impacts the dashboard slicer's usability. For example, a client with only three years of data, the slicer appears 70% blank. If the filter is set to a shorter period (e.g., 3 years) for usability, any historical data that is backloaded later will not be captured by the Data Export service. This can break integrations used for critical analysis, such as baselining.
• Operational Risk: Wide distribution of setting accessibility poses a significant risk of end-users unknowingly breaking essential data integration logic

Proposed Solution

To resolve these issues, the Data Export temporal filtering should be decoupled from the ‘Dataset Maximum Time period’ setting

This can be accomplished by either:

1. Creating a separate setting parameter specifically for the Data Export function, which would not have a 10-year maximum restriction
2. Defaulting all Data Export tables to automatically capture all available data, removing the filter from the export process entirely

Implementing this solution will ensure data integrity for our clients, improve the platform's front-end usability, and make our data integrations more robust and reliable.