Forum Discussion
Active Gateway and Connection, but the semantic model cannot find the connection
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.
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.