The premise of our product (QQube™) is to elminate the need for using cumbersome connectors, becuase of the need to know tables, relationships, connecting strings, reverse engineering etc.
We have a traditional star schema data warehouse for QuickBooks, and have created 'shells' for each subject. (Subjects are independen, and minimize any need to create "cross FACT" analysis.) We install several ODBC drivers, and have shells for many products, e.g. powerpivot, access, crystal reports, etc. so that people can just open up a shell and never once have to deal with a connector. They don't have to spend time figuring out the nuts and bolts - they can just start dragging their fields into the canvas.
All shells for all products use the same ODBC connectors, so that if one person creates a dashboard/pbix file on one desktop, all they have to do is send the pbix file to someone else who has our product, and then they can refresh with their own data - never once, having to create a new connection of any sort - or having to recreate the dashboard/layout.
So once we create the shells using one of our ubiquitous ODBC connectors, anybody should be able to (a) install the on-premise or personal gateway, then (b) create something using one of the shells we have provided, and (c) hit the publish button to get it going. (Obviously they have to create the PowerBI Pro account before doing so).
We have checked, and double checked, and somebody in the community found a workaround, which intimates that there is a bug. The workaround is to upload the files FIRST, then install the on-premise gateway; then everything works fine. This is repeatable.
The problem is, we can't upload any other shells, after the gateway is in place.
And no, the Get Data>Local Files also didn't work.
Several customers have reported that using the personal gateway works most, but not all, of the time.
We would like to be able to give customers simple instructions to use our product seamlessly with PowerBI Pro to refresh their data automatically, but unfortunately, we will have to wait until this is fixed - or somebody can find the nature of the problem.
Not trying to be "salesy' or create a pitch here (we just want this to work), but if you want to see how we interface with your product you can go here to one of our guides: https://clearify.com/wiki/view/1422/connecting-to-qqube
