Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Reply
Anonymous
Not applicable

Orders vs target when target is on higher level then orders

Hello,

 

I've created a model where I have Persons in a Team that can create orders. The teams have a target for the amount of orders, but the persons don't. 

 

When I create a visual that gives the amount of orders and the target per year, it seems to work. When I use the slicers on the team, the orders and targets are sliced correctly. 

But, when slices on Persons, the data is not correct. The orders are sliced correct, but the target stays at the level of the teams. 

 

So, with the data form the example attached:

Orders 2018: 104 (42 for team 1 and 62 for team 2)

Target 2018: 81 (29 for team 1 and 52 for team 2)

 

When Sliced on team, the above numbers are correct. When sliced on Person, target doesn't change (try slicing Z.Z., target stay at 81). 

 

Desired output:

Don't know for sure, but a desired output could be that the line dissapears from the visual (i.e. target = 0 when sliced on person).

Other ideas for output are also welcome.

 

P.s. in the real data I have targets on months, 25 teams and more than 100 persons. So thats makes a lot of rows.

 

Example data

https://1drv.ms/u/s!AvC8sXOgGhuRqXIsCmHe2xKYd7ud?e=Tm9iZG

2 ACCEPTED SOLUTIONS
TomMartens
Super User
Super User

Hey @Anonymous ,

 

you can create a measure like this:

_Target = 
IF(
    ISFILTERED('Person'[Person])
    , BLANK()
    , CALCULATE(SUM('Target'[Target]))
)

and use this measure for the line chart.

 

Maybe this article provides some additional insights on how to handle different granularities:

https://www.daxpatterns.com/handling-different-granularities/

 

Hopefully, this provides some insights and new ideas on how to tackle your challenge.

 

Regards,

Tom



Did I answer your question? Mark my post as a solution, this will help others!

Proud to be a Super User!
I accept Kudos 😉
Hamburg, Germany

View solution in original post

Fowmy
Super User
Super User

@Anonymous 

You can hide the line when you select a value in the Persons column by replacing your Target in the visual with the following measure:
I suggest you split the target by person based on your business logic, then you will have orders and target per person in the same visual.

 

Target_M = 

IF(
    ISFILTERED(Person[Person]),
        BLANK(),
        SUM(Target[Target])
)

 

 

________________________

Did I answer your question? Mark this post as a solution, this will help others!.

Click on the Thumbs-Up icon on the right if you like this reply 🙂

YouTube, LinkedIn

Did I answer your question? Mark my post as a solution! and hit thumbs up


Subscribe and learn Power BI from these videos

Website LinkedIn PBI User Group

View solution in original post

3 REPLIES 3
Fowmy
Super User
Super User

@Anonymous 

You can hide the line when you select a value in the Persons column by replacing your Target in the visual with the following measure:
I suggest you split the target by person based on your business logic, then you will have orders and target per person in the same visual.

 

Target_M = 

IF(
    ISFILTERED(Person[Person]),
        BLANK(),
        SUM(Target[Target])
)

 

 

________________________

Did I answer your question? Mark this post as a solution, this will help others!.

Click on the Thumbs-Up icon on the right if you like this reply 🙂

YouTube, LinkedIn

Did I answer your question? Mark my post as a solution! and hit thumbs up


Subscribe and learn Power BI from these videos

Website LinkedIn PBI User Group

TomMartens
Super User
Super User

Hey @Anonymous ,

 

you can create a measure like this:

_Target = 
IF(
    ISFILTERED('Person'[Person])
    , BLANK()
    , CALCULATE(SUM('Target'[Target]))
)

and use this measure for the line chart.

 

Maybe this article provides some additional insights on how to handle different granularities:

https://www.daxpatterns.com/handling-different-granularities/

 

Hopefully, this provides some insights and new ideas on how to tackle your challenge.

 

Regards,

Tom



Did I answer your question? Mark my post as a solution, this will help others!

Proud to be a Super User!
I accept Kudos 😉
Hamburg, Germany
Anonymous
Not applicable

Thanks!!

 

It was easier then I thought 🙂

Helpful resources

Announcements
November Power BI Update Carousel

Power BI Monthly Update - November 2025

Check out the November 2025 Power BI update to learn about new features.

Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors
Top Kudoed Authors