Forum Discussion
Dynamic Column Name
Hi Ta_Weiss,
Glad to hear you managed to resolve the dynamic column name part using Field Parameters and calculated measures that’s a smart DAX-based workaround. Regarding the Power Query step error (“Value rename operations is expected”), it usually occurs when the Table.RenameColumns syntax isn’t recognized correctly because of localization (for example, needing semicolons instead of commas).
The correct format is:Table.RenameColumns(PreviousStepName, {{"OldColumnName", NewNameVariable}})Make sure you use double braces { { } } and your regional delimiter settings match Power BI’s M language.
For your second question on parameter snapping this behaviour is expected with list-based parameters. In the latest Power BI Desktop, the What-If parameter has been renamed to Numeric range. You can create it from Modelling → New parameter → Numeric range.
Set your data type (Whole / Decimal), min, max, and increment values (e.g., 0 → 10 000 by 1). Click Create Power BI will add a parameter table, a slicer, and a measure. Place the slicer on your page. Users can now type or slide any numeric value freely (e.g., 500) without snapping to the nearest item.
This is the same functionality as the old What-If parameter, just with a new name. Microsoft documentation: https://learn.microsoft.com/en-gb/power-bi/transform-model/desktop-what-ifThank you for using the Microsoft Fabric Community Forum.
Hi Ta_Weiss,
Thank you for reaching out to the Microsoft fabric community forum. Also, thanks to Zanqueta, for his inputs on this thread. I reproduced the scenario, and it worked on my end. I used it as sample data and successfully implemented it.
outcome:
I am also including .pbix file for your better understanding, please have a look into it.
Hope this clears it up. Let us know if you have any doubts regarding this. We will be happy to help.
Thank you for using the Microsoft Fabric Community Forum.
Hello v-kpoloju-msft ,
The last step doesnt work for me:
It says value rename operations is expected.
Also, could you advise on second part of my question?Hello v-kpoloju-msft
Update: Feel free to give update on the glitch I sent in my previous reaction for benefit of other users, but I managed to solve my issue by creating a field parameter containing my calculated measures and instead refering to their names in quiotation marks, I reffered to calculated field for the month or year.
If you could advise on the parameter list behaviour described below, that would be also super useful.Hi Ta_Weiss,
Glad to hear you managed to resolve the dynamic column name part using Field Parameters and calculated measures that’s a smart DAX-based workaround. Regarding the Power Query step error (“Value rename operations is expected”), it usually occurs when the Table.RenameColumns syntax isn’t recognized correctly because of localization (for example, needing semicolons instead of commas).
The correct format is:Table.RenameColumns(PreviousStepName, {{"OldColumnName", NewNameVariable}})Make sure you use double braces { { } } and your regional delimiter settings match Power BI’s M language.
For your second question on parameter snapping this behaviour is expected with list-based parameters. In the latest Power BI Desktop, the What-If parameter has been renamed to Numeric range. You can create it from Modelling → New parameter → Numeric range.
Set your data type (Whole / Decimal), min, max, and increment values (e.g., 0 → 10 000 by 1). Click Create Power BI will add a parameter table, a slicer, and a measure. Place the slicer on your page. Users can now type or slide any numeric value freely (e.g., 500) without snapping to the nearest item.
This is the same functionality as the old What-If parameter, just with a new name. Microsoft documentation: https://learn.microsoft.com/en-gb/power-bi/transform-model/desktop-what-ifThank you for using the Microsoft Fabric Community Forum.