Fundraising Types - List and Query roadblocks

@Tasha Mikoz:

Hi all,

After some thoughts and insights on the following issues I keep having.

When creating lists and wanting to exclude specific fundraisers (let’s say Bruce), this isn’t an option due to the following:

• If I select all, this will include the one fundraiser Bruce that I don’t want, but also includes all that don’t have a fundraiser assigned, which I do want
• If I was to select the fundraisers that want individually, I can’t then get all those whom have no fundraiser assigned as because they have no type assigned, they’re excluded by default
  • I’m after a way to include specific fundraisers AND those that don’t have any assigned.
    • “Bruce” in our case is like an external that runs his own portfolio, but within our database.

I’m thinking of assigning a fundraiser type: No Fundraiser assigned, so that in lists I can be specific around whom I want and don’t in the lists, which are often connected to workflows.

Then, for query:

We currently have two options for fundraiser types when there is an active fundraiser attached: Primary or Secondary (ignoring the above pargraphs)

• Always only one Primary
• Always only one Secondary

Once a fundraiser is removed and “inactivated as the fundraiser on the record” they have no type assigned.

Having some roadblocks with writing queries for fundraisers where they’ve previously been assigned to donor, but are no current, and have no end date on them. We introduced using end dates a few months ago but there’s just too much data to wade through where we have no record of that date, using exclusions on queries isn’t possible for this scenario as the data is inconsistent.

If I was to add another fundraiser type “ZZ” and apply this to the fundraisers record on the donor card where inactive, when I run queries, I would be able to accurately narrow down whom was a previous fundraiser by using that type, since I can’t use the end date.

Any thoughts or repercussions on these suggestions?

Thanks! ?

This is a lot.

Even though I don't know how you are using Lists in webview, I would advise to NOT create a “No Fundraiser Assigned” type. You are adding a lot more work to maintain that information, and I wonder if the advantage of having the workflow is worth it.

I always recommend the following when it comes to fundraiser assignments:

• Assign a Fundraiser Type for every assignment. When an assignment is over, change the type to a “former” version, such as “Primary - Former”.
• Assign a “date from” all of the time
• Assign a “date to” whenever you change a type to a former version

This alone will help a lot with your queries and exports. I never use webview to mark a solicitor as “former” because it doesn't do enough to help you query and export cleanly.

This is definitely an instance where managing your data with a light hand will actually be more useful. Don't overcomplicate it - it doesn't need to be that much work.

Karen