Forum Discussion
Active Gateway and Connection, but the semantic model cannot find the connection
Hi!
I have a Gateway and an ODBC connection done through that. Both are online and active. I'm admin in everything.
However, when I try to link the Connection to Semantic model, I can't find the connection (or any) where I could map to.
I have tried this now multiple times with different organizations and different reports.. For example with organizational web file this is wokring.
Have you faced the same problem?
Problem solved. I've struggled with the same thing before, so I'll write the solution here, in case I think about it again in a couple of years. (or if someone else is facing the same problem)
The name of the ODBC connection created on the computer must be the same as the name of the Gateway in Power BI Service.
This is very odd, because Gateway's name makes quite a silo. Several connections with different names can pass through the GW, but every time an ODBC connection is used on a desktop to create a report, the connection must have the same name as the GW. -> If one has several ODBC connections, one must be always changing the names.
I don't know if it's the same with other connections.
3 Replies
- aj1973
Community Champion
Hi amira_achek
ODBC is not a Source of your semantic model. What is the data source? Oracle?
- amira_achekNew Member
Hi, the data source is from Amazon (Web Services(?)), but I actually solved my problem already. I'll write the solution as a response to my question.
- amira_achekNew Member
Problem solved. I've struggled with the same thing before, so I'll write the solution here, in case I think about it again in a couple of years. (or if someone else is facing the same problem)
The name of the ODBC connection created on the computer must be the same as the name of the Gateway in Power BI Service.
This is very odd, because Gateway's name makes quite a silo. Several connections with different names can pass through the GW, but every time an ODBC connection is used on a desktop to create a report, the connection must have the same name as the GW. -> If one has several ODBC connections, one must be always changing the names.
I don't know if it's the same with other connections.