Pledge date precedes campaign

Hi Julie,

It sounds like you’re getting the error because the new Fund is not associated to any Campaign on the pledge date you’re trying to enter. (Even though you will be changing the Campaign to FY12 when you process the pledge, the system is trying to default to the Campaign your Fund is associated to on your pledge date.)

I think this workaround will give you what you need:

1.       Associate the new Fund to the FY11 Campaign. You may also need to reactivate the Campaign if you’ve change the Status to Closed.

2.       Process your pledges with the correct pledge dates. Associating the new Fund to the earlier Campaign should take care of the error message, and you’ll be able to choose your FY12 Campaign from the dropdown.

3.       After you’ve closed your Batch, remove the association between the new Fund and the FY11 Campaign. (This step isn’t technically necessary, but will be helpful for keeping your Campaign setup clean and making it clear that your Campaign/Fund structure changed between FY11 and FY12.)

I hope that helps!

…Alex

Alex Harris | Patron Development Manager | 206.443.2210 x1018 | Fax: 206.443.2379
SEATTLE REPERTORY THEATRE | www.seattlerep.org | In Lower Queen Anne at Seattle Center

2011-12 SEASON SUBSCRIPTIONS ON SALE  Click here!

From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Julie Eskind
Sent: Friday, July 29, 2011 2:45 PM
To: Alex Harris
Subject: [Tessitura Development Forum] Pledge date precedes campaign

We have recently reformatted our organization-wide accounting structure and, accordingly, have changed our development structure in Tessitura.  We have created all new funds with all new GL codes for our FY12 campaigns.

Here's the problem: 

We have pledges that predate the FY12 campaign start date (i.e. an April pledge to a campaign that begins at the start of our fiscal year on June 1).  We have set up the FY12 campaigns and have associated the respective new funds, all with start and end dates of our fiscal year, June 1 - May 31.  Our appeals and sources for the related efforts go back before campaign start date and before any of the FY12 pledge dates, so earlier efforts can be tracked. 

But when processing the pledges, we are unable to backdate it to a date before the campaign start date.  We get an error stating that the chosen fund is not associated with a campaign.  If we do the exact same thing with the current date as the pledge date it works just fine, but we want to keep the original pledge date on the record.

Any ideas?

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Hi Julie,

It sounds like you’re getting the error because the new Fund is not associated to any Campaign on the pledge date you’re trying to enter. (Even though you will be changing the Campaign to FY12 when you process the pledge, the system is trying to default to the Campaign your Fund is associated to on your pledge date.)

I think this workaround will give you what you need:

1.       Associate the new Fund to the FY11 Campaign. You may also need to reactivate the Campaign if you’ve change the Status to Closed.

2.       Process your pledges with the correct pledge dates. Associating the new Fund to the earlier Campaign should take care of the error message, and you’ll be able to choose your FY12 Campaign from the dropdown.

3.       After you’ve closed your Batch, remove the association between the new Fund and the FY11 Campaign. (This step isn’t technically necessary, but will be helpful for keeping your Campaign setup clean and making it clear that your Campaign/Fund structure changed between FY11 and FY12.)

I hope that helps!

…Alex

Alex Harris | Patron Development Manager | 206.443.2210 x1018 | Fax: 206.443.2379
SEATTLE REPERTORY THEATRE | www.seattlerep.org | In Lower Queen Anne at Seattle Center

2011-12 SEASON SUBSCRIPTIONS ON SALE  Click here!

From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Julie Eskind
Sent: Friday, July 29, 2011 2:45 PM
To: Alex Harris
Subject: [Tessitura Development Forum] Pledge date precedes campaign

We have recently reformatted our organization-wide accounting structure and, accordingly, have changed our development structure in Tessitura.  We have created all new funds with all new GL codes for our FY12 campaigns.

Here's the problem: 

We have pledges that predate the FY12 campaign start date (i.e. an April pledge to a campaign that begins at the start of our fiscal year on June 1).  We have set up the FY12 campaigns and have associated the respective new funds, all with start and end dates of our fiscal year, June 1 - May 31.  Our appeals and sources for the related efforts go back before campaign start date and before any of the FY12 pledge dates, so earlier efforts can be tracked. 

But when processing the pledges, we are unable to backdate it to a date before the campaign start date.  We get an error stating that the chosen fund is not associated with a campaign.  If we do the exact same thing with the current date as the pledge date it works just fine, but we want to keep the original pledge date on the record.

Any ideas?

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!