The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Solved! Go to Solution.
Hi @Nildatt_Jadhav ,
Thanks for posting your query in the Microsoft Fabric Community. I have reviewed your scenario and set up the unit conversion using a disconnected slicer along with a DAX measure. When you use the Unit Table slicer (Base / Thousand / Lakh / Crore), the Amount_Scaled measure updates accordingly to display the correct values.
FYI:
For additional details, please refer to the attached PBIX file. Feel free to reach out if any future adjustments are needed.
Regards,
Yugandhar.
thanks Yugandhar.
One more thing how i can able to apply the same for multiple column value through single slicer setting. example - value in different column such as Sell value, max value, Year till date, etc.
Hi @Nildatt_Jadhav ,
If you want to keep columns like Sell Value, Max Value, and YTD Value separate but scale them all at once with a single slicer, it's best to create separate DAX measures for each column using the same scaling logic. This way, your layout stays the same and the slicer applies the scaling to each measure consistently.
If you prefer to display these values dynamically like switching between Sell, Max, and YTD in one chart or filtering by metric you can unpivot the columns in Power Query. This will turn them into a single Metric Type column and a related Value column, both controlled by a slicer.
Thank You.
Hi @Nildatt_Jadhav ,
Could you let us know if your issue has been resolved or if you are still experiencing difficulties? Your feedback is valuable to the community and can help others facing similar problems.
Hi @Nildatt_Jadhav ,
Thanks for posting your query in the Microsoft Fabric Community. I have reviewed your scenario and set up the unit conversion using a disconnected slicer along with a DAX measure. When you use the Unit Table slicer (Base / Thousand / Lakh / Crore), the Amount_Scaled measure updates accordingly to display the correct values.
FYI:
For additional details, please refer to the attached PBIX file. Feel free to reach out if any future adjustments are needed.
Regards,
Yugandhar.
User | Count |
---|---|
15 | |
8 | |
6 | |
6 | |
5 |
User | Count |
---|---|
23 | |
13 | |
13 | |
8 | |
8 |