This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
All,
I have been struggling with how to best evaluate something in my organization. Currently when we sell to a customer, we may ship to multiple sub customers as part of the master purchase order. So in PowerBI I will have multiple PONumbers for multiple customers, but they are still part of one master PO. For example, we may have master PO#001 for the master customer, but then we put a letter after the sub orders like PO#001A, PO#001B and PO#001C for the subcustomers. I want a way to identify all the times in which an order has a master and sub POs attached. The kicker is that I also want to only identify it as being a part of a master PO if there are multiple customers in the PO. Sometimes we use that logic for delayed shipping to one vendor.
The way I worked it so far is that I first created a new calculated column off of PO that removed the far right character if it was not a master PO.
PONumberBase = if(ISBLANK([MasterPONumber]),iferror(Left([PONumber],LEN([PONumber])-1),""),[PONumber]
I then used the following formula in my table to create a calculated column that would get at I want, but it is telling me that I have a circular dependency.
MasterPOCheck= if(CALCULATE(DISTINCTCOUNT([CustomerInternalID]),Revenue[PONumberBase]=Earlier([PONumberBase]))>1,"Master PO","Single PO")
I may have explained this poorly, but any ideas on what I could do differantly?
Thanks!
Alex
Solved! Go to Solution.
Thanks @Eric_Zhang. I actually was able to figure it out. I did the following adjustment to my second formula.
MasterPOCheck= if(CALCULATE(DISTINCTCOUNT([CustomerInternalID]),filter(Revenue,[PONumberBase]=Earlier([PONumberBase]))>1,"Master PO","Single PO")
Thanks again.
Alex
@adcook wrote:
All,
I have been struggling with how to best evaluate something in my organization. Currently when we sell to a customer, we may ship to multiple sub customers as part of the master purchase order. So in PowerBI I will have multiple PONumbers for multiple customers, but they are still part of one master PO. For example, we may have master PO#001 for the master customer, but then we put a letter after the sub orders like PO#001A, PO#001B and PO#001C for the subcustomers. I want a way to identify all the times in which an order has a master and sub POs attached. The kicker is that I also want to only identify it as being a part of a master PO if there are multiple customers in the PO. Sometimes we use that logic for delayed shipping to one vendor.
The way I worked it so far is that I first created a new calculated column off of PO that removed the far right character if it was not a master PO.
PONumberBase = if(ISBLANK([MasterPONumber]),iferror(Left([PONumber],LEN([PONumber])-1),""),[PONumber]
I then used the following formula in my table to create a calculated column that would get at I want, but it is telling me that I have a circular dependency.
MasterPOCheck= if(CALCULATE(DISTINCTCOUNT([CustomerInternalID]),Revenue[PONumberBase]=Earlier([PONumberBase]))>1,"Master PO","Single PO")
I may have explained this poorly, but any ideas on what I could do differantly?
Thanks!
Alex
It sounds that you‘ll have to re-model your data. To have a better understanding on your idea, could you post some sample data? Even better you can share a pbix file with sample data.
Thanks @Eric_Zhang. I actually was able to figure it out. I did the following adjustment to my second formula.
MasterPOCheck= if(CALCULATE(DISTINCTCOUNT([CustomerInternalID]),filter(Revenue,[PONumberBase]=Earlier([PONumberBase]))>1,"Master PO","Single PO")
Thanks again.
Alex
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 35 | |
| 33 | |
| 26 | |
| 22 | |
| 18 |
| User | Count |
|---|---|
| 66 | |
| 36 | |
| 32 | |
| 26 | |
| 23 |