Migrating Custom Datasets between OAC Environments

Question

In OAC, I have created a custom dataset that uses an OTBI subject area as its data source. I have then used that dataset as my data source for an OAC workbook. When I migrate the workbook from our SIT environment to our UAT environment, the dataset remains connected to the SIT OTBI data source. I then have to go into the workbook and replace the Dev1 dataset with the Dev2 equivalent dataset. Am I doing something wrong? Is there any way to get the workbook migration to see that there is an existing data set from a different source that it could identify and adopt on its own without me having to replace the dataset manually?

Daniel Ryan · Accepted Answer

Hi

It sounds as though you are using dedicated connections for Dev1 and Dev2. If you just had a single OTBI connection, you could update the connection details when you migrate and then reload the data at the dataset level rather than having to create a new dataset and change it in the workbook.

I don't think there is a way of deriving the URL dynamically based on the source like there is in workbooks but I might be wrong.

RVohra · Accepted Answer

As a workaround, if you don’t need a custom dataset (no joins, transforms, snapshots):

* Build the workbook directly on the OTBI subject area
* Let environment-specific OTBI connections handle themselves

This avoids the dataset layer entirely and migrations become much cleaner.