1 Excluding people from data view who are in a family with someone in a certain group 1 Michael Garrison posted 9 Years Ago I'm trying to accomplish something which technically is a little esoteric, but I think the goal is rather within the realm of what should be doable... I have a data view for our financial ministry so they can see when someone has contributed for the first time, so they can track growth in that area. Since we have just started using Rock, we created a group and filled it with people who have given at least once before while we were using the old system (we called the group "SK givers"). The data view then is set up to show people whose "first contribution date" is between two given dates AND who are not also in the SK Givers group. That way, we can modify the "First time contributors" data view by changing the dates to be between two arbitrary dates and get a list. So that works. The issue is that under the old system, there was no concept of "combine giving with" like there is in Rock. Say for example that my wife has always been credited with all of our family's giving. Now if I am for whatever reason credited with this week's contribution, that data view will include me as a first-time giver, even though my family has been giving for years. We'd like to have the data view exclude anyone who is in the same family as someone who is in that SK givers group. I don't see any built-in functions in the Data Views to accomplish something like that. I considered creating another data view which would return everyone in the same family as a member of that group, but there are some limitations to that too... first, there's no "family members" post-filter transformation. Maybe that would be a useful feature to add? Second, there's no "NOT in existing data view" option as a filter- I KNOW that would be useful! Short of creating some custom SQL to create such a quasi-report, is there another workaround to get to what I'm trying to accomplish? Without having access to Rock's date control as a block, I'm not thrilled with how error-prone an input-to-parameter-driven page would probably be and I'd love for this function to stay within the realm of a real Rock Data View.