Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Good day beautiful people,
I have dataset and live connected report to it.
My main issue is that the report data is slightly different and I have no idea how to validate, where the change occurs.
Dataset table:
Customer Name | Customer ID | Value Checked | Check Key |
microsoft | 123456 | microsoft | Customer Name must be in capital letters |
Apple | 789456 | Apple | Customer Name must be in capital letters |
sony | 764542 | sony | Customer Name must be in capital letters |
Report table:
Customer Name | Customer ID | Value Checked | Check Key |
MICROSOFT | 123456 | MICROSOFT | Customer Name must be in capital letters |
APPLE | 789456 | APPLE | Customer Name must be in capital letters |
sony | 764542 | sony | Customer Name must be in capital letters |
Microsoft - incorrect
Apple - incorrect
Sony - correct
This table is designed to list all the Customer Names, which failed to pass the Check Key test. In this very example, I'm checking if the Customer Name is in capital letters.
The issue I have, is that there are 2 records which are not correct between dataset and report, while 900+ are still correct and showing correct values.
In the report table both Microsoft and Apple should NOT be in capital letters, just like in dataset table.
I have refreshed DB, dataset, report, PQ few times but this error keeps persist.
To continue testing, I have made new table and filtered it just to show the troublesome records - in dataset everything is fine, while report still shows incorrect stuff.
What could happen in the report, that could change just these 2 records? I've tried to lookup for any changes or data modification things but since it is live connected, most of the options are disabled.
Solved! Go to Solution.
Hi @Copycat ,
Case sensitivity is one of the more confusing aspects of Power BI: while the Power Query engine is case sensitive, the main Power BI engine (that means datasets, relationships, DAX etc) is case insensitive.
Maybe you can change the connection mode of your dataset or add some tag to help recognize these data in your data source and the use the DAX function UPPER or LOWER to transform your data.
For more details, please refer to:
Power BI And Case Sensitivity - Chris Webb's BI Blog (crossjoin.co.uk)
Best Regards,
Jianbo Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Copycat ,
Case sensitivity is one of the more confusing aspects of Power BI: while the Power Query engine is case sensitive, the main Power BI engine (that means datasets, relationships, DAX etc) is case insensitive.
Maybe you can change the connection mode of your dataset or add some tag to help recognize these data in your data source and the use the DAX function UPPER or LOWER to transform your data.
For more details, please refer to:
Power BI And Case Sensitivity - Chris Webb's BI Blog (crossjoin.co.uk)
Best Regards,
Jianbo Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Check out the September 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
103 | |
98 | |
98 | |
38 | |
37 |
User | Count |
---|---|
152 | |
121 | |
73 | |
71 | |
63 |