Normal 0 false false false MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;}

 Hi,

I'm pretty new to RE, but have some experience with this type of system. We have a distinct group of donors called FOF or Friends of the Friendless. This is often listed under attributes. I can't get a consistent number when I pull them based on the attributes.

I don't know if this is way to vague to get any help...but any would be appreciated.

Thank you,
Amy

I am not sure what you mean when you say "this is often listed under attributes"  You'll need to know if it is the place where you code FOF constituents or not.

If this is the code - depending on where you are pulling from there may be some automatic filtering happening.  If you simply run a constituent query on these attributes and leave all the checkboxes at the top checked you will get every constituent record with that code.  If you uncheck some of those boxes your number may change.  If you run an individual query or an organization query it will only give you those constituent types and your number may change.

If you are using one of the features in Mail you need to know that Mail often automatically filters out any record where there is no address with the send mail box checked.  You may also be filtering out inactives, deceased, and has no valid address.

If you are using a report - again it may be filtering on something that you do not realize.

You'll need to be more clear about the different places you are getting inconsistent numbers from for us to be more helpful.

Another thing you'll want to check if you're using an attribute is to see if it is set up to only allow one per record in case you may have put the same attribute on a constituent multiple times (which could scew your counts)

If you're pulling them into a query you'll need to be clear about what you're asking for and if it can supress duplicates - Depends also on what you're displaying if it is a multi-valued field. I find it's always safer to use export if you're not confident with the file structure.