Problem Statement
Currently, Export Actions and Saved Views are not dynamically synchronized after an Export Action is created. This limitation creates additional maintenance effort for model builders and increases the risk of inconsistencies between export configurations and reporting requirements.
Key Challenges
1. Saved View Changes Are Not Reflected in Existing Export Actions
When developers modify a Saved View, such as updating filters, adding or removing line items, or changing row and column selections, the associated Export Action does not automatically adopt these changes.
As a result, developers are often required to create a new Export Action or manually reconfigure the existing one to align with the updated Saved View. This increases development effort and maintenance overhead, particularly in models with numerous exports and integrations.
2. Export Action Updates Require Reconfiguration
Changes made directly within an Export Action are not automatically reflected in the existing Export Action configuration, often requiring developers to recreate the action to incorporate the updates.
This behavior introduces additional administrative effort and can lead to inconsistencies between the intended export output and the actual action configuration.
Benefits
- Reduces the need to recreate Export Actions.
- Minimizes manual maintenance and administrative effort.
- Improves consistency between Saved Views and Export Actions.
