"The table has no visible columns and cannot be queried." error when refreshing semantic model in Power BI Online
I'm unable to refresh my Power BI Semantic Model on Power BI Online and am running into the error below. I’m using the QuickBooks Power BI Connector.
Data source error{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":s{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"The table has no visible columns and cannot be queried."}}....
The semantic model is tied to my Profit & Loss Standard Report, which was generated using the CreateReportSchema Stored Procedure, and works fine on Power BI Desktop. How can I resolve this issue?
Page 1 / 1
The error of "The table has no visible columns and cannot be queried" indicates the Power BI Gateway is unable to retrieve the data associated with this semantic model. This issue can occur when the schema file tied to the semantic model is inaccessible.
For context, our Connectors automatically store schema files at the path specified within the Location connection property, which is set to %APPDATA%\CData\QuickBooksOnline Data Provider\Schema by default, as seen in our documentation linked below.
This default location is inaccessible to the Power BI Gateway service account. Therefore, you will want to update the Location property to an accessible path. To do so, open your DSN Configuration, select Advanced, and scroll down to the Schema section to set the Location property. An example can be seen below; I created a QB Schema folder in my Public Documents in this case.
Click OK to save your changes. Then, you'll want to transfer any previously generated schema (RSD) files (located at the default location of %APPDATA%\CData\QuickBooks Data Provider\Schema) to the new path specified in the Location property.
After following these steps, Power BI Gateway should be able to access the schema files and retrieve the metadata/data to properly refresh the semantic model.
Note, while this post refers to the QuickBooks Power BI Connector, this is applicable to all of our on-premise Power BI Connectors.
If the issue persists after following the steps above, reach out to us at [email protected] and we'll be happy to help.
