Forum Discussion
Enterprise Gateway - Cannot connect to the mashup data source
- 7 years ago
I figured out the issue. While PBI Desktop can navigate Snowflake's different schemas correctly, apparently the PBI Gateway cannot. Once I changed the data sources to all be from the same schema, the gateway was able to refresh without issue. I'm not sure why we utilized different schemas in the first place, but I'll keep this in mind down the road.
I figured out the issue. While PBI Desktop can navigate Snowflake's different schemas correctly, apparently the PBI Gateway cannot. Once I changed the data sources to all be from the same schema, the gateway was able to refresh without issue. I'm not sure why we utilized different schemas in the first place, but I'll keep this in mind down the road.
What did you do to "changed the data sources to all be from the same schema"?
Can you give little detail how you did that. Do you mean that you consolidated data coming from different sources to once single source? SQL database, excel spreadsheet, etc in to one?
- jeffhadley7 years agoFrequent Visitor
Hi Brian,
In snowflake, views are setup in different 'schemas'. So we have some views setup in a PBI schema and others that house similar information setup as ETL schemas (there's also a PSA schema). I'm VERY new to using Snowflake and probably haven't done as much homework as I should to understand it all. One of my reports utilized a data source that was a PBI view (employee attributes) and another source was using an ETL view (location attributes). Since I also had a PBI view that provided the location attributes I needed, I changed my data source to pull from the PBI view instead of the ETL view, which solved my mashup issue.
- Anonymous7 years agoNot applicable
Thaks for posting the details. What I do to getaround mashup data is:
When you bring in the tables from different data sources, I make a reference table of each original table. Then I run queries against the reference table and leave the original alone. This work for me.