topic Re: A child can't be both removed and included lakehouse in Developer

A child can't be both removed and included lakehouse

jaryszek — Mon, 29 Sep 2025 08:34:14 GMT

Hello,

I am getting error like here:
"A child can't be both removed and included"

The remote semantic model is connected to OneLake flavour source.
Everything is working properly, remote semantic model is updated properly, I can use tables which i added in my connected reports.

But why I am getting this? It is concerning...

best,
Jacek

Re: A child can't be both removed and included lakehouse

v-tejrama — Tue, 30 Sep 2025 09:54:27 GMT

Hi @jaryszek ,

Thank you for bringing this to my attention. The error “A child can’t be both removed and included” typically indicates a discrepancy between the Lakehouse schema and the semantic model, often caused by the removal or renaming of tables, columns, or relationships in the Lakehouse without corresponding updates in the semantic model.

To resolve this, please:

Open the semantic model and use Edit tables to synchronize it with the latest Lakehouse schema.
If you have recently dropped or renamed any columns or tables, ensure they are removed from the semantic model and then re-added as needed.
Check your workspace’s System storage for outdated semantic models or orphaned artifacts that may persist after changes to the Lakehouse. Removing these often helps resolve such issues.

If these steps do not resolve the error, recreating the semantic model is a reliable option that will not impact your data but will ensure the metadata is properly aligned.

For further guidance, you may find the following articles useful:

Best regards,
Tejaswi.

Re: A child can't be both removed and included lakehouse

jaryszek — Tue, 30 Sep 2025 10:12:06 GMT

Sorry but edit tables is not working on DirectLake over OneLake...

Re: A child can't be both removed and included lakehouse

v-tejrama — Tue, 30 Sep 2025 10:34:46 GMT

Hello again @jaryszek ,

The error “A child can’t be both removed and included” typically appears when there is a mismatch between your Lakehouse schema and the semantic model metadata. Since the “Edit tables” option is not available in DirectLake over OneLake, resolving this requires a different approach. Please verify if any tables or columns in your Lakehouse were recently renamed or deleted while still being referenced by the semantic model or reports. If so, consider restoring the items or updating the reports accordingly. Creating a new semantic model and reconnecting the reports often resolves the issue by removing outdated metadata. Additionally, if there are duplicate or orphaned references to the same table, cleaning these up can help. If these steps do not resolve the problem, it is advisable to raise a support ticket with Microsoft so they can further investigate any potential backend issues in your workspace.

We appreciate your ongoing efforts in testing the solutions provided. Given that several approaches have been tried without success, we recommend submitting a support ticket to the Microsoft product team for more detailed assistance. You can submit a request using the following link:Power BI Partners | Microsoft Power Platform.

If you find a solution through support, sharing your experience with the community would be greatly appreciated, as it may assist others facing similar challenges.

For additional support, you may also consider connecting with a Microsoft Power BI partner for guidance on implementation or consulting.

Best regards,
Tejaswi.

Re: A child can't be both removed and included lakehouse

Simonsabin2 — Sun, 22 Mar 2026 16:01:32 GMT

This occurs when the you have tables that are listed in the PBI_RemovedChildren atrribute of the expressions.tmdl in your model AND the table is also referenced as a table in your table\*.tmdl files

I had this when trying to have role playing dimension. It appears that PBI desktop can't handle this and it causes an error.

To get it working remove the offending entry from that expressions.tmdl file.