Quantcast
Channel: Power Query topics
Viewing all articles
Browse latest Browse all 31110

Data Gateway - determining what data is being pulled back

$
0
0

I'll start by saying this is probably pretty similar to posts that already exist, but my search skills are failing me.  

I have a Dataset that uses SQL, anonymous web, and an excel file. 

 

I have setup the On-Prem Data Gateway, and from the PowerBI > Manage Gateways page, everything is reporting as online and "Good to Go".

I have three datasources setup in the Gateway.

  1. an anonymous Web request (timeanddate.com)
  2. SQL Server to the database in question
  3. "Folder" to the root folder of local directory of the excel file's storage location (using my windows username and passwords for the login)

In my PBIX file I have these three sources setup

  1. an anonymous Web HTML page
  2. a SQL server connection in 'import connectivity mode'
  3. an Excel file with the full path to the desired excel file

 

I have run several refreshes after publishing this setup to the Power Bi Service.  My gateway connection is still showing as using the 'data gateway' and refresh history shows that all of them have completed.

 

I've watched 'open files' on the server hosting the excel file and I can see it get accessed by my user account when I do an on-demand refresh.

 

However, there are no updates to my 'online' dataset'

 

I've tried looking at the Data Gateway logs, but I can't make real heads or tails out of what's being recorded there. 

 

In short, everything 'seems' to be working properly, but data is missing in my charts.  I know that it is because I put some dummy data in the excel file and those results have yet to show in the graphs or in "Explore >See data"

Additionally the widget that utilizes the anonymous web request has yet to update either. 


I'd appreciate any pointers on what I'm doing wrong.


Viewing all articles
Browse latest Browse all 31110

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>