Membership Overlap Report

Chris Wallingford This was so helpful, thank you!

Now the only problem I'm running into is I wanted to be able to click into each group but it's returning everyone from that area. For example, if I were to click into the SR Donor/Membership Levels and Film Center Membership overlap I'd get the entire 265 SR Donors/Members instead of just the 4 I was hoping to see. Anyway to fix that?

Hi Elizabeth,

Good news and maybe some bad news at the end. Good news first... thank you for asking this. Using Multi-Pass Aggregation in the way that I did above, the grouping on [Constituent ID] would override the _Constituents jump to grouping on Constituent ID, and include everyone from the source row rather than just the constituents in the row and column from which you jumped. I dug a little deeper and was able to find a formula that worked around this. It seems that if we use this formula instead...

( [# of unique Constituent ID] , [Constituent ID] )

...where the latter [Constituent ID] field uses the "Attribute" filter from above, we get both the same result in our cross-over counts, and the jump to is successfully filtered by both the row and the column.

Note there are a total of 6 Film Center members, and 4 of them are also SR Membership... the results on the _Constituents jump to align:

I am excited about this, so thanks again for asking. However, there's still the potential bad news. This just came up here, and I thought for sure that in v15, the filter would not transfer to the _Constituents dashboard. I just tested though, and it worked. Hopefully that will reliably work for you as well, but if not, we can consider that defect I reference in the linked post to be resolved in v16.

Thanks for the positive start to my day today.

Hi Elizabeth,

Good news and maybe some bad news at the end. Good news first... thank you for asking this. Using Multi-Pass Aggregation in the way that I did above, the grouping on [Constituent ID] would override the _Constituents jump to grouping on Constituent ID, and include everyone from the source row rather than just the constituents in the row and column from which you jumped. I dug a little deeper and was able to find a formula that worked around this. It seems that if we use this formula instead...

( [# of unique Constituent ID] , [Constituent ID] )

...where the latter [Constituent ID] field uses the "Attribute" filter from above, we get both the same result in our cross-over counts, and the jump to is successfully filtered by both the row and the column.

Note there are a total of 6 Film Center members, and 4 of them are also SR Membership... the results on the _Constituents jump to align:

I am excited about this, so thanks again for asking. However, there's still the potential bad news. This just came up here, and I thought for sure that in v15, the filter would not transfer to the _Constituents dashboard. I just tested though, and it worked. Hopefully that will reliably work for you as well, but if not, we can consider that defect I reference in the linked post to be resolved in v16.

Thanks for the positive start to my day today.

I read Nathaniel's post and then this one and it reads like a thriller. Great job. V16 here we come

Chris Wallingford this is so helpful, thank you! When I put this advanced filter in I'm getting a syntax error. I imagine I'm missing something from your screenshot. Would you mind copying and pasting that into our chat here?

Hi Elizabeth.

It's this one from earlier up in this thread.

{
 "attributes": [
 {
 "dim": "[MEMBERSHIP LEVEL.Membership Organization]",
 "filter": {
 "members": [
 "SR Membership (AD)"
 ]
 }
 }
 ],
 "custom": true
}