This semantic model contains calculated tables or calculated columns that refer to remote tables

[lafakios]

Hi,

I have a report based on a composite model, including imported data and direct query.

Initially, the report had a calculated table based on the direct query and a calculated column in the data set of the direct query.

When trying to publish the report, I was getting the below warning:

"This semantic model contains calculated tables or calculated columns that refer to remote tables, which will result in refresh failures after publication"

I then deleted the Calculated Table as well as the Calculated column.

As the Calculated Column was required by the report, it was added by the semantic model onwer in the native data model by using the same column name and DAX.

I had then to delete the initial Direct Query from the report's data model and I reconnected to it in order to get in the model the newly added attribute.

When trying to publish the updated report (which did not have any calculated table or calculated column based on the DirectQuery), I got again the same warning.

Would you know how to overcome this issue? 

Could this be related to any metadata that does not refresh after all the above changes which have been performed in the report?

Could this be caused by the fact that the newly added column in the underlying semantic model has the same name with the former Calculated column?

Thanks in advance for your help.

Regards,

Akis

[lafakios]

Hi,

Thanks for your help.

The PBIX contains a very complicated report with several data sets and visuals. 

It is unfortunately not straightforward to recreate it from scratch. 

Would there be any way to force the refresh of the internal model JSON?

Regards,

Akis

[v-priyankata]

Hi @lafakios,

Please verify if any of your existing data sources are using unsupported data source. Currently, Incremental refresh for semantic models in Power BI - Power BI | Microsoft Learn is supported for composite models connecting to SQL, Oracle, and Teradata data sources only.

Additionally, the following Live Connect tabular sources can't be used with composite models:

• SAP HANA
• SAP Business Warehouse
• SQL Server Analysis Services earlier than version 2022
• Monitor report usage metrics - Power BI | Microsoft Learn

Finally, Using streaming semantic models in composite models isn't supported.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Thanks.

[v-priyankata]

Hi @lafakios 
Could you let us know if you have tried the suggestion above, and if the issue still persists?

[lafakios]

Hi,

I have tried all suggested actions and the issue still persists.

Rebuilding the PBIx is not possible as it is a very complicated report.

Regards,

Akis

[v-priyankata]

Hi @lafakios 
If that is the case then please reach out to support team to find out the root cause of the issue
we regret the inconvenience caused Kindly raise a support ticker here How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn.

Thanks.

[v-priyankata]

Hi @lafakios 
I hope you’ve submitted the support ticket. Once you receive a solution, please share it here so it can help others facing the same issue. If you have any further questions, feel free to reach out to the community.

Thanks.

[v-priyankata]

Hi @lafakios 

I hope the information provided was helpful. If you still have questions, please don't hesitate to reach out to the community.

[lafakios]

Hi,

Thanks all for your input.

The reports uses SQL and Semantic Models as data sources.

I have tried all suggested actions and the issue still persists.

Rebuilding the PBIx is not possible as it is a very complicated report.

Regards,

Akis

[lafakios]

Hi,

I have followed all above steps.

I have even reconnected to the remote table which now has the newly added column with a different name (so that it does not match the name of the former calculated columnt).

Further to the above, I have also cleared the files in the C:\Users\<you>\AppData\Local\Temp\Power BI Desktop folder. 

When trying to publish, I still get the same error.

Regards,

Akis

[v-priyankata]

Hi @lafakios 

Thank you for reaching out to the Microsoft Fabric Forum Community.
@MohamedFowzan1 Thank you so much for your inputs.

Even though no calculated table or column shows up in Power BI Desktop, the internal model JSON can still keep those old definitions. Desktop doesn’t complain, but when you publish, the Power BI Service checks the metadata more strictly and still sees them that’s why the warning keeps coming back.

Try the suggestion from user that create a new PBIX & connect only to the remote semantic model, re-import your imported tables & measures. rebuild the visuals.

If I misunderstand your needs or you still have problems on it, please feel free to let us know. 

Thanks.

[MohamedFowzan1]

Hi @lafakios 

This looks more of like a cache issue:

Clear and Refresh Metadata Cache

Close and reopen Power BI Desktop to clear in-memory cache.

In Power Query Editor, refresh all data sources and applied steps.

Consider clearing Power BI Desktop cache manually:

Go to File > Options and settings > Options > Data Load > Clear cache.

Then, Reimport or Reset the Connection Exactly

Also try changing the column or table name once just to make sure no meta data is affecting this and use a fresh pbix incase you still face issues.