Categories
- All Categories
- 75 Oracle Analytics News
- 7 Oracle Analytics Videos
- 14K Oracle Analytics Forums
- 5.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 40 Oracle Analytics Trainings
- 59 Oracle Analytics Data Visualizations
- 2 Oracle Analytics Data Visualizations Challenge
- 3 Oracle Analytics Career
- 4 Oracle Analytics Industry
- Find Partners
- For Partners
Option to not Overwrite Objects When Importing DVAs
When you import a DVA into OAC, if the DVA contains a workbook, data set, or connection that shares the name of an existing workbook, dataset, or connection, you only have the option to cancel the import or overwrite the pre-existing object. The notification message also does not specify which type of object or which object specifically would be overwritten.
I believe that you should have the option to append a tag (like (1), date, or choice) to the object's name upon import. The message should at least tell you what object will be overwritten if you chose to import anyways. I've included a screenshot of the import warning/message.
Comments
-
This would be a great addition to OAC. Having those objects having to be overwritten leads us to do some development in our production environment entirely to avoid that happening. The other option we sometime use is to export a workbook from Classic as a .catalog file as that does seem to work as well. But, if you have added an additional data set to go along with existing ones going that route does not work.
0 -
When we are exporting from one environment(Test) to another environments (Production) , connection details changes and overwrites. It should be resolve it .
0 -
Complete lack of flexibility/support of Dev2Prod processes for DV objects represents the biggest weaknesses in DV. I am pointing to it for pretty long time - see for example:
So I desperately hope, that improvements in this area will come very soon...
0
