When we import a table with Power BI, we are getting "nested tables" as columns which are for any referential integrity foreign keys. That is to say that they keys are from other tables which reference the one we query.
When that happens, Power BI then tries to get Primary Keys and other structure information from those related tables. And it does this without us asking it to. A "feature", I'm sure.
However, not all of those tables are accessible by the powerbi gateway service account, and should not be.
So the call for DDL information fails, and we get the error while refreshing the data set.
Does anyone know how to turn that behavior off in Power BI?
The workarounds I can come up with are not so great: (1) grant access to objects and hope nobody notices; (2) break (remove) the foreign key definitions and hope other projects aren't impacted; (3) create entirely new objects that are identical to the original without any such key relationships ... and hope everyone remembers to use those for Power BI instead of the objects used by all other programs.
