Hoping some consortium types can help with this one. For our consortium we have implemented a constituency to determine whether a customer record is a legitimate contact for one or more organization. The constituency is managed by the standard Tess utility designed for that purpose and seems to be working correctly.
We had an odd circumstance today where a box office manager built an extraction and made a suppression segment like so:
Constituency Not In <my organizations's customer constituency>
When he generates extraction counts (logged in under his organization's control group) that segment only suppresses around 5800 records. The bottom line totals seem correct however.
When I generate counts logged in as an admin, it suppresses what I expected, around 110,000 records. The bottom line results are the same as before.
What is there in extraction manager that would cause this? We are perplexed.
Hi Levi,
Does this work as expected for the other consortium members or even someone else at this user's organization? Just trying to focus in on extent of the problem. Do you utilize constituency-based security where this user might not have access to certain records to begin with due to their constituency? The fact that it works for you as an admin sounds like evidence of a security issue. That's the only thing I can think of if this suppression is "ignoring" certain records.
~Dan
This is probably because the NOT IN statement will filter out any constituent that has the correct organisation constituency (ie has has access to) and has another constituency associated with it
Try using DOES NOT HAVE rather than NOT IN and hopefully then his count should drop to 0 and yours as admin should drop by 5,800.
Mark
Thank you all (and Anna W.) for the help. Using "Does Not Have" resolved the oddness.
I never have to use extractions myself, but it might be time for me to play around with them a bit more :)