Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Solved! Go to Solution.
@Anonymous , Couple of reasons I can think of.
1. These measures are coming from different tables and one of them have a problem with project join
2. Both table has project ID, and there is a common project table(Project Dimension) and you took project or project name from a fact, not from Dimension
3. One of the measures is using all/all selected. even possible when they are from the same table
Hi,
Does this work?
=if(isblank('Baseline'[Baseline - CapEx]),blank(),MAX( 0,'Baseline'[Baseline - CapEx] - [Forecast CapEx]))
@Ashish_Mathur It works in terms of producing the numbers I want, but the solution I found earlier was to bring fields in from a table other than my project fact table. Thank you.
Hi @Anonymous
Can you please provide more info with screenshots, input and required output in table format for the community so that you ask can be better understood and resolved quickly.
Hope it resolves your issue? Did I answer your question? Mark my post as a solution! Appreciate your Kudos, Press the thumbs up button!! Linkedin Profile |
@pranit828 No, I can't actually, due to confidentiality. I was hoping that someone would recognize the behavior and maybe provide some clues as to what could be causing this behavior.
If that's not you; thanks anyway for trying.
@Anonymous , Couple of reasons I can think of.
1. These measures are coming from different tables and one of them have a problem with project join
2. Both table has project ID, and there is a common project table(Project Dimension) and you took project or project name from a fact, not from Dimension
3. One of the measures is using all/all selected. even possible when they are from the same table
@amitchandak Good call! It looks like using the Project ID and some other fields from a fact table was causing the problem.
Thank you.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
68 | |
54 | |
53 | |
36 | |
34 |
User | Count |
---|---|
84 | |
71 | |
55 | |
45 | |
43 |