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.
I'm trying to create a projected deadlines column but each tasks date is dependent on the previous task and there are set # of days itll take for each task to be completed. I was able to create a calculated deadline utilizing the logic above but it cannot go farther than the last completed deadline so I was looking to have my new projected deadline (to show when the rest of the project could be completed if everything goes well) reference itself in a column but thats giving me a 'circular dependency'. So I wanted to know if I would have the same problem if I were to do it in separate tables and have a one column in each to reference each other instead (technically still doing the same work just in another table and having it reference off of different table instead)
So realistically, each task can only be completed if the prior ones before it were completed as well. The order is different on what task is dependent on another so I have it set where I made them unique identifiers using an ID. The Calculated deadline is this DAX code -
@Anonymous
Can you please paste some sample data to work with?
Hi @Anonymous
This is a complex subject as dax does not support recursive calculations. Nevertheless, this is sometimes possible ising some mathematics. Usually it is expensive in terms of performance. Please share more details and I'll see if anything can be done.
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 |
---|---|
14 | |
11 | |
10 | |
10 | |
10 |
User | Count |
---|---|
16 | |
13 | |
12 | |
11 | |
8 |