Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Option to select connection when importing DVA file
Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):
Description (Required): When exporting a workbook based on a SQL query, the options are to include or exclude connection details. If the details are excluded, when the workbook is imported and opened, username./password is required which cloud developers may not have. If the details are included, a new connection is created that points back to the original environment.
When importing a DVA, there should be an option to use an existing connection
Use Case and Business Need (Required): When migrating content between environments, there is no easy way to use an existing data connection in the new environment
Enhancement Request / Service Request:
Comments
-
100% agree - this is a frustrating functional gap that has caused many problems when you have multiple environments using different connections. Importing projects should be able to use connections in the target environment without entering any passwords.
0 -
I am 100% agree and vote for this Idea. Deployment mechanism for transferring DV workbook (and related artefacts) from one environment to another (DEV2PROD) using DVA package, should be much more "smarter" than current status.
Beside the option to choose existing connection when importing DVA packages, import should also allow to keep original namespace of imported data sets from "source" environment (instead of changing it to namespace of user logged in on target environment).
0
