Forum Discussion
Model changes not updated in downstream model
Hi Anonymous , thank you for reaching out to the Microsoft Fabric Community Forum.
The renaming of measures in M2 is the core issue. Renaming measures creates ambiguity for Power BI’s dependency tracking. When M1 is updated, the measure lineage in M2 doesn’t reconcile properly, as Power BI uses internal IDs to manage dependencies, and renaming disrupts this. The Error: "Expected ModelingEngine to block any changes with MashupDocument impact" suggests a conflict or pending changes in the underlying dataset that prevents a clean refresh or re-selection of M1 as a data source.
Please consider below:
- In M2, identify the renamed measures that were sourced from M1. Revert the measure names in M2 to match those in M1. Refresh M2 to ensure the changes propagate correctly. After this, you can create aliases or display names for the measures in reports instead of directly renaming them in the model.
- Download the updated M1 model and republish it. Create a fresh M2 model by selecting the updated M1 as its source. Re-add any calculated tables or additional measures specific to M2. This ensures a clean lineage and resolves dependency issues but requires manual effort.
If this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.
Community SupportHi Anonymous , thank you for reaching out to the Microsoft Fabric Community Forum.
The renaming of measures in M2 is the core issue. Renaming measures creates ambiguity for Power BI’s dependency tracking. When M1 is updated, the measure lineage in M2 doesn’t reconcile properly, as Power BI uses internal IDs to manage dependencies, and renaming disrupts this. The Error: "Expected ModelingEngine to block any changes with MashupDocument impact" suggests a conflict or pending changes in the underlying dataset that prevents a clean refresh or re-selection of M1 as a data source.
Please consider below:
- In M2, identify the renamed measures that were sourced from M1. Revert the measure names in M2 to match those in M1. Refresh M2 to ensure the changes propagate correctly. After this, you can create aliases or display names for the measures in reports instead of directly renaming them in the model.
- Download the updated M1 model and republish it. Create a fresh M2 model by selecting the updated M1 as its source. Re-add any calculated tables or additional measures specific to M2. This ensures a clean lineage and resolves dependency issues but requires manual effort.
If this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.
Thank you very much, I did not find this in the documentation. It seems a bit ill advised that it is possible to change the names in dependent models in the first place, in my opinion.