-
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
This is the controller panel for Smart Panels app
[OPT-5393] Overwrite entities on import to prevent duplication
| Link | New: This issue is depended on by SUPPORT-10822 [ SUPPORT-10822 ] |
| Description |
New:
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. Which problem are you going to solve with this functionality? 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. *Hint:* Eventually before export the user would have to specify a Report / Dashboard / Alert Business Key or similar that uniquely identifies the entity such that across environments it is clear which entity is being updated. Currently such ID does not exist, but each environment automatically creates unique IDs on creation. |
| Mentioned Roles |
| Mentioned Groups |
| Description |
Original:
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. Which problem are you going to solve with this functionality? 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. *Hint:* Eventually before export the user would have to specify a Report / Dashboard / Alert Business Key or similar that uniquely identifies the entity such that across environments it is clear which entity is being updated. Currently such ID does not exist, but each environment automatically creates unique IDs on creation. |
New:
*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. *Which problem are you going to solve with this functionality?* 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. *Hint:* Eventually before export the user would have to specify a Report / Dashboard / Alert Business Key or similar that uniquely identifies the entity such that across environments it is clear which entity is being updated. Currently such ID does not exist, but each environment automatically creates unique IDs on creation. |
| Mentioned Roles |
| Mentioned Groups |
| Labels | New: potential_for_3.8 |