-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
2
-
S
-
3 - Expected
What is the desired functionality that you are missing?
As a User I would like to have a functionality in Optimize that allows me to overwrite / update a specific existing report / dashboard / collection / alert when importing a JSON specification so I can synchronize development and production instances.
Which problem are you going to solve with this functionality?
I want to, given a user-defined unique identifier, evaluate how current a given entity is and update it, if necessary.
Currently whenever I import a JSON specification of an Optimize entity I automatically create a new Optimize entity. While this is the expected result in some cases, in other situations this behaviour is not ideal.
Use Case: Change a filter before re-downloading the report (OPT-3404)
Note: Upon export, an entity (Collection/Report/Dashboard/Alert) must have a user-defined unique identifier such as a Business Key to en. Currently such ID does not exist, but each environment automatically creates unique IDs on creation.
Revised Scope:
Use a key that defaults to the reportId/dashboardID to identify reports and always overwrite reports with matching keys.
AT:
- Import overwrites reports/dashboards in the same scope (eg when importing into a collection) with the same key
