This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowThe Fabric community is upgrading! Read all of the details including the timeline and what you can expect. Learn more
Why sometimes columns are perceived as a SUM and sometimes not? is that related to the data source (in this case Excel)?
Thanks!
Solved! Go to Solution.
It has to do with the data type - if the data looks like a number then PBI will assume it can be treated like a number. If you want to stop that behavior then go to the query editor and explicitly define that column as a text column.
It has to do with the data type - if the data looks like a number then PBI will assume it can be treated like a number. If you want to stop that behavior then go to the query editor and explicitly define that column as a text column.
I have the oppisit problem. Is there any way to get PBI to understand that a column (with numeric values) to be a measurement? I have tried different data types but nothing happens.
Yeah i had that same problem! I solved it by 'geting data' again, replacing the old tables with new ones and he understood the columns from new tables as a measurement.. idk why. But ofc this is not a good solution!
Here's the story with the query editor - don't let it choose the data types for you. The query editor always inserts that second step "Changed Type". Delete that and go through and set the data types yourself.
If you set the column to numeric and run the query it will show up as a number (that you can sum up) on your field list. If that's not happening then there's some problem that needs to be reported to Microsoft.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
| User | Count |
|---|---|
| 27 | |
| 22 | |
| 20 | |
| 18 | |
| 14 |
| User | Count |
|---|---|
| 25 | |
| 20 | |
| 20 | |
| 20 | |
| 20 |