What are the default filters?
When we first set you up we ask you a few questions. The more we know the more specific your setup will be. But if we only have a little information we'll set you up in a default way. Here we will look at those defaults. This is just informational, you can make changes to your settings. For more information on the filter settings see Using Contact Filters
When we are told legacy fields but not given anything more
When someone says they are using legacy fields or maybe they say they are using the demographics page then we know not to use contacts. In this case we'll set them up like this: 
When we are told legacy fields and given some non-standard phone and or email fields
Sometimes someone sends us phone/email fields they'd like to use. If these fields include even 1 non-standard field (i.e. custom and not from StudentCoreFields) then we'll need to make a custom data plugin that has a special query that references those fields. So that current selections know to use that custom query instead of the standard one we'll mark them as Custom Query using Legacy
If the list of phone/emails does not include any of the standard fields we'll disable them from exports as well.
When we are told that you are using Contacts
We ask legacy fields or contacts and have more questions based on what you answer. But most of the time when you say contacts it's easier to set you up with a default set of filters and then let you change to what makes sense to you. We can go over the options in training and that's often easier than trying to explain over email. In these cases we'll start you with these settings:
When do we use Custom Query using Contacts?
For the most part thats no longer needed. Generally speaking we need it for 2 situations.
- Your data plugin is before version 9. In this case we need the system to look for that custom query for the custom language field
- You have a custom filter, one that isn't an option in the Base. This is getting more and more rare as we try to put options in so you don't need to customize. If you aren't customized you can make your own changes easier. But in the case you do need a custom filter your default settings would look like this
What about custom languages?
Starting in version 9 of the data plugins you no longer need a custom query if the only thing custom is the language. We've been able to isolate that for current selections so that you can use the latest queries without needing to rebuild your plugin each time.
In version 9 of the Base 2 plugin we also added in a way for you to know that you are using a custom language. Many times people forget what field is being used and ask us and we have to decode the plugin which isn't a problem but does mean you have to wait for an answer. Now you have a way of checking what language field is being used. Putting a field in the box doesn't make the query use it, we manually put the value in as a reference for you later if you need it. 