Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowTry your skills in the Power BI Dataviz World Championship! Round one ends June 26. Join now
Hi
I need Some input.
I have some reports in PBI desktop using orcale Dev env (schema name = DEVUSER), published to PBI workspace DEV.
I want to create deployment pipeline which deploy code from Dev workspace to UAT workspace.
UAT env - the oracle db is on different server and a different user from Dev.
I created on-prem gateway and two connections one for DEV (different user and different oracle server) and I created another connection in PBI service for UAT which has different user and different server than DEV.
I created Rules where I can change the connection strings as below:
When I deploy reports and refresh the model I get this error message:
What am I missing.
The reports in UAT workspace still shows the data of Dev env.
Please can you ehlp!
Solved! Go to Solution.
Mixed connection give a lot of problems even without pipelines.
Glad you were able to figure out. Don't forget to Mark the correct answer só it can help others even if it is your own.
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em Português
since this report is based on a local data and you are using a gateway to connect to your Oracle DB believe that the questions is around the connection to the new gateway connection.
Believe that your problem is around the user, you refer that you are using a different user? Is that different user on a different gateway or just a different user on the DB?
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsThanks.
Dev env reside in a different oracle server.
UAT env reside in a different oracle server than DEV.
Both have different username and password.
Although the oracle db objects on both env are the same but the schemas (user) are different.
When I check the model in PBI service they look to point to a different Getway/Connection. Dev is connected to the right On-prem-connection (Dev) and for UAT is connecting to the right On-prem-connection (UAT) so this works.
I get slightely different error now.
Not sure what am I missing.
Thanks for your help!
Hi @XhevahirMehalla ,
Apologies for the following question, but I got some issues with similar things. Is the tables/views used in DEV environment already implemented in UAT enviroment of Oracle DB?
Asking this because it seems like the connection is passing but is not finding specific tables or views.
Did you test to update the UAT model in Power BI desktop?
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsYes, they are the same tables/views. The names are not changing. The schema names/username and server name. Different env basically.
Aftert I refresh the UAT model after has been deployed using the Deployment Pipeline it fails now.
I think is the right approach. You have to refresh the model at the target in order to get the data from the UAT env.
Using the parameters in PBI desktop I created a parameter as SchemaName and created a List of Values (Dev username and UAT userName). I think am I doing the right thing.
Thanks
Xhev
Hi @XhevahirMehalla,
I need to do some tests but the approach seems to be the correct one. when you go to the setting of the UAT do you have the Data Source Credentials correct or are they giving login error?
Asking this because the following dataset properties are also not copied during deployment:
Role assignment
Refresh schedule
Data source credentials
Query caching settings (can be inherited from the capacity)
Endorsement settings
So you may need to go to the UAT Enviroment and check the credentials / gateway connection.
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsThe UAT connection in PBI Service for UAT worksapce shows that is picking up the correct Connection. In PBI service I have two connections (Dev connection) and UAT connection and using the same on-premise Gateway and both of these are online.
This the gateway and seem online:
and then is the DEV and UAT connection. Both connections using the same Gateway ( each having different user DEV=DevUser and UAT=UATUser and of course a different password.
On the Deployment pipeline I changed added rules by using SchemaName=UATUserName
What am I missing?
I can see on the model on each workspace is showing that under the correct Connection Name (On-Prem Connection) so is picking up the correct db server but maybe the user is not picking up the user.
Does it have to be the same user?
I run out of options now.
Thanks
Hi @XhevahirMehalla ,
Let me try on my side to check what can be happening.
Just to check you have:
Is this correct?
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsMy reply is in orange:
Just to check you have:
Maybe I am missing smth.
Maybe in PBI desktop I missing something but according to the docs and some other info got from you guys I was asked to setup Parameters as SchemaName.
Thanks
Xhev
I think I found the issue.
On PB desktop I had a mixed connection and I changed this for one table:
FROM:
let
Source = Oracle.Database("10.110.16.87:1521/nonprod_fcubs.nonproddb.spokenprdvcn.oraclevcn.com", [HierarchicalNavigation=true]),
JBDEV = Source{[Schema="JBDEV"]}[Data],
ICTM_ACC1 = JBDEV{[Name="ICTM_ACC"]}[Data]
in
ICTM_ACC1
TO:
let
Source = Oracle.Database("10.110.16.87:1521/nonprod_fcubs.nonproddb.spokenprdvcn.oraclevcn.com", [HierarchicalNavigation=true, Query="select * from ictm_acc"])
in
Source
Once I changed this then I can see the report is refreshed and I can see the data is flowing from DEV to UAT and I can see different output.
Mixed connection give a lot of problems even without pipelines.
Glad you were able to figure out. Don't forget to Mark the correct answer só it can help others even if it is your own.
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsDon't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 24 | |
| 22 | |
| 21 | |
| 20 | |
| 14 |
| User | Count |
|---|---|
| 59 | |
| 52 | |
| 41 | |
| 33 | |
| 32 |