Power BI Gateway Not Refreshing Dataset Due to Localhost Mapping

[nlgupta]

Hi everyone,

I created a Power BI report on my local machine using tunneling, where my data source was mapped to localhost. I then published the report to the Power BI Service.

After that, I set up a Power BI gateway cluster on an AWS Windows machine and created the data source gateway in Power BI Service. However, when I tried to refresh the dataset, the gateway could not establish a connection because the report is still mapped to localhost (from when I created it on my local machine).

Since the published dataset retains the original localhost mapping, the gateway on the cloud machine cannot correctly reference the actual data source. How can I resolve this issue and correctly map the dataset to the cloud-hosted gateway?

Any guidance would be greatly appreciated.

Thanks in advance!

[nlgupta]

Hi @lbendlin ,Thanks for the response.

The PostgreSQL database is hosted on AWS. I created the report on my local machine and fetched the data in Power BI using tunneling (due to project security restrictions), which mapped the database host to my localhost.

After publishing the report to Power BI Service, I set up a Power BI gateway on an AWS Windows machine that has direct access to the database. However, I am unable to map the dataset to the configured gateway cluster (data source).

Do I need to publish the report again from the AWS Windows machine for the gateway to work correctly? Or is there another way to resolve this issue?

[lbendlin]

It's not a problem with the gateway. The problem is that you host the database on a machine that is inaccessible to the gateway.

Move the database to an accessible location.

[nlgupta]

Thanks for the response.

The PostgreSQL database is hosted on AWS. I created the report on my local machine and fetched the data in Power BI using tunneling (due to project security restrictions), which mapped the database host to my localhost.

After publishing the report to Power BI Service, I set up a Power BI gateway on an AWS Windows machine that has direct access to the database. However, I am unable to map the dataset to the configured gateway cluster (data source).

Do I need to publish the report again from the AWS Windows machine for the gateway to work correctly? Or is there another way to resolve this issue?

[lbendlin]

Use parameters to modify the connection string in the semantic model. 

[nlgupta]

Yes Got it, replacing localhost connect details with the help of parameters. also do have any reference link or article for updating data source details with parameters.

Thank you 

[lbendlin · Accepted solution]

How to Parameterize Data Sources in Power BI | phData