https://community.fabric.microsoft.com/t5/Custom-Visuals-Development/Visualizations-failed-to-load/m-p/1587409#M3511 <P><SPAN>Using the column that’s being renamed, but in Power BI model, I never renamed it. Power BI refresh will be successful, but some visualisations will fail to load:</SPAN></P><P>&nbsp;option 1. The easy one :&nbsp; rename in&nbsp; Power BI model, the renamed-at-source field, to its original name.&nbsp; all visualisations and DAX calculations will become valid again.</P><P>&nbsp;</P><P>However that is not a feasible solution as the visual needs to have the new column name.&nbsp;</P><P>&nbsp;</P><P>The other option is to go over all invalid visualisations and DAX calculations, and edit them to use the new field name.&nbsp;</P><P>This method is also not the seamless way to go.&nbsp;</P><P>&nbsp;</P><P>Any other suggestions?</P> Fri, 08 Jan 2021 07:09:46 GMT Vino13 2021-01-08T07:09:46Z https://community.fabric.microsoft.com/t5/Custom-Visuals-Development/Visualizations-failed-to-load/m-p/1587409#M3511 <P><SPAN>Using the column that’s being renamed, but in Power BI model, I never renamed it. Power BI refresh will be successful, but some visualisations will fail to load:</SPAN></P><P>&nbsp;option 1. The easy one :&nbsp; rename in&nbsp; Power BI model, the renamed-at-source field, to its original name.&nbsp; all visualisations and DAX calculations will become valid again.</P><P>&nbsp;</P><P>However that is not a feasible solution as the visual needs to have the new column name.&nbsp;</P><P>&nbsp;</P><P>The other option is to go over all invalid visualisations and DAX calculations, and edit them to use the new field name.&nbsp;</P><P>This method is also not the seamless way to go.&nbsp;</P><P>&nbsp;</P><P>Any other suggestions?</P> Fri, 08 Jan 2021 07:09:46 GMT https://community.fabric.microsoft.com/t5/Custom-Visuals-Development/Visualizations-failed-to-load/m-p/1587409#M3511 Vino13 2021-01-08T07:09:46Z