A published composite model requires the powerbi dataset to be part of the gateway

[Anonymous]

I made a composite model of an on-premises analysis services tabular model together with a powerbi dataset stored in the service. The analysis tabular model has an on-premise gateway connection which works well. 

When using the direct query mode, which creates a local model, combining the powerbi dataset and the tabular model looks to work fine on the desktop. When publishing, moving to the gateway>settings it says the powerbi dataset should be part of the same gateway as the analysis model. It has a red cross in front of it.

So this looks odd to me:

- it shouldn't be needed to add a powerbi dataset to the on-premise gateway because it is already in the cloud

- and if i try i don't get it to work

As a result the deployed report might not work correct.

[Anonymous]

Hi @GilbertQ thanks for the response. 

It is an analysis service on-premise which acts via the gateway. 

I combine it with a powerbi dataset. In the desktop it works  well, once published, when i want to query the published dataset via excel i get the following response once connectiing

When looking in the gateway settings of the dataset it says the powerbi dataset should be added to the same gateway as the analysis services

[Anonymous · Accepted solution]

Oke it works fine now.

I had to enter the data source references for the powerbi dataset. 

Although it still shows a red cross in the gateway section for the powerbi dataset (not for the on-premise analysis service) the dataset is refreshable and usable in reports

[GilbertQ]

Hi @Anonymous 

Is the "The analysis tabular model has an on-premise gateway connection which works well. " a Azure Analysis Services database?

If so I am not sure if you can have a composite model that can go via your On-premise gateway because the gateway used for Azure Analysis Services is different from the Power BI On-premise gateway.