
1. Re: Pie Chart from Caclulated Field
Adolfo Hernandez Oct 8, 2018 9:47 PM (in response to Manuel Kavekos)Hello Manuel,
I think I found a solution however I am not sure if it would work with new data or if it could be scalable. First I made a duplicate of your data source within Tableau and joint both tables using the Member ID field on each of them:
From the second table I just kept the Domain field identified in the workbook as Domain(Sheet11). Then I made a reference table to create my calculations (Sheet 9):
As you see by doing a crossjoin we get all the combinations of categories within the Domain field by each Member ID but we just need one row per Member ID, if the Member ID has just one Domain category we use it asis but if there's more than one Domain category per Member ID we need to filter the duplicate combinations or the single combinations (look at the table for more clarity). So, to do this, I assigned a value to each DomainDomain (Sheet11) category combination, by doing so we can filter the row that we need.
Basically we need the rows where the *Combined Domain Filter field is equal to 2 and *Combined Domain Filter is (equal to 1 AND Domain is different to Domain (Sheet11). To do this first we need a calculation that gets the maximum value for each Member ID and repeats it on every row of each Member ID, we do this with a FIXED LOD calculation, field *New Domain:
In the picture below I have arranged my calculated fields as 1,2,3; those number are the sequence as I created them. Hopefully you will understand my explanation . If not you can ask me. The final result is as below:
Let me know if this solves the problem, thanks!\
Cheers
Adolfo

2. Re: Pie Chart from Caclulated Field
Manuel Kavekos Oct 10, 2018 11:53 PM (in response to Adolfo Hernandez)Thank you Adolfo for the quick and creative response. I've been working through this and can see this working as an option for this data set but the issue will still be working with new data. The data I am working with will be updated at least monthly and think I need a solution that doesn't require as many calculated field combinations nor a self join. I did get some ideas as you've provided a creative solution but still want to continue with a different approach if you or anyone else has other ideas.