How To Accelerate Deployment Of Power BI Reports For OBIEE Or OAC From Dev To Prod Environment
Are you going through the cumbersome process of recreating the reports in Power BI everytime you connect to a new OBIEE or Oracle Analytics Cloud(OAC) environment (typically Dev, UAT and Prod)?
If your answer is yes, it doesn’t have to be so laborious. There is a much easier and faster way to move reports from Development to production environments. The process doesn’t have to be cumbersome anymore!
For instance, let’s assume a report is developed from scratch initially in Power BI and it’s configured to fetch data from one of the environments (say Dev). Now the same report can be brought to life with data from other environments (UAT or Prod) just by simply pointing the data source to the corresponding environment, rather than redeveloping the report for each of the environments.
With BI Connector, this is achieved in a matter of seconds. The need to redevelop the reports is eliminated, and hours of effort is saved!
Before we jump into the steps, it is important for you to know the existing type of connectivity used by BI Connector to connect the OBIEE environments and Power BI. It should be either through
- ODBC protocol (or)
- The custom connector of BI Connector listed in Power BI (highly recommended)
If you’re using BI Connector via ODBC protocol, please follow these steps after developing the report for the Dev environment –
- Navigate as below in Power BI Desktop –
File -> Options & Settings ->Data Source Settings -> Data Sources in current file
- Select the existing DSN
- Click the Change Source button
- In the dialog box that opens up, select the DSN of the corresponding OBIEE environment, and click Ok
- Click Close
- Click Refresh in Power BI Desktop to load the data from the selected environment
There you go!
If you’re using BI Connector as a custom connector in Power BI, please follow these steps after developing the report for the Dev environment –
- Open the ODBC Data Source Administrator in Windows
- Select the DSN of the Dev environment, and click configure
- Change the connection credentials alone – server name, port number, username and password pointing to the new Data Source (UAT or Prod environment) and don’t make any change to the DSN
- Click the test connection button and validate the connection. Successful connection shows the below message
- Click Save and Ok
- Open Power BI desktop and clear the cache (Refer this article on clearing cache in Power BI)
Note – Though this step is optional, it is highly recommended as a proactive step to avoid loading the cached data
Now hit refresh on the Power BI report. Sit back and watch it loading data from the desired environment.
Interested in speeding up your OBIEE report creation and deployment using Power BI and BI Connector?
Subscribe to BI Connector
Get the latest BI Connector news, articles, and
resources, sent straight to your inbox every month.