Letter and Mail
Often, when i go back to use the letter in Mail, i get the message "NO records meet specified crteria!"
OR, i edit a letter, changing font, size margins, etc, go back to Add-ins, save it and when I go back to remerge the batch, the letter is still in the original font and size.
I understand that Mail and the letters in the table in Config are not related (this makes no sense either). I have taken the online Mail courses and watched the tutorials. This remains a frustrating mystery.
HELP, please.
Marcia
Comments
-
Marcia - What might be happening here is that when you're in Mail and perform the merge, it's not really saving the merge function anywhere. Sounds like you're just performing the merge each time.
I'd suggest trying this: Create an export and for format, choose Blackbaud Conditional Word Merge. Set up your merge document(s) here, save the export. Then run the export and see if it is retaining the formatting, etc. You should then be able to save the exported letters, so you can then go back and open them.0 -
Yes, I will second Gina for her response. I went into the Config, and added Letter Descriptions for each of my desired letters (I have about 10-12, generally sorted by the funding area, and this way when I'm entering the batch, I ensure I can put the letter type in the batch.) Then, follow Gina's notes below using the Conditional Word Merge set up each letter. It takes a bit of time, but it is so worth it in the end! I spent a few hours getting each one just right, and now I can zip through them when I do the merge.0
-
Marcia, I've gotten the 'no records meet specified criteria' response occasionally, too. And I may find reason quickly like forgot to change query of records to include or it might take longer to find the reason as the fund is not included in the criteria. It does seem like there is always a reason for 'no records.' They're already acknowledged/receipted, date range could be issue, SC or MG criteria was accidentally changed, criteria set wrong, etc.0
-
Small world! We are having the same problem as we speak, and are stumped. We have a case open right now, and none of the usual suspects seem to be causing this. I'll let you know what it turns out to be for us, and maybe it will be something obscure nobody thinks to check.0
-
After chatting with Support, the consensus for us is that some parameters preventing this letter from pulling may have been changed from inside the Word Merge Wizard that cannot be changed from outside of it, and then the Mail template was saved. This sounds relevant in your case, Marcia, because our support rep specifically asked us if we were doing a Conditional merge after we sent him screenshots of all of the tabs in that Mail template, and the gift itself, and he found nothing amiss. I could not answer that question for him; Problematically, we can't go in and change said theoretical setting, or even see if the merge is Conditional, because the Wizard won't let us get that far. The best solution we have right now is to delete it and set up a new one from scratch.
It seems odd to me that this would be possible at all. We should not be able to irrevocably break a Mail template. Limiting parameters should always be available without having to actually execute a merge.0 -
We get "No records meet specified criteria" for conditional mail merges that we have marked "Acknowledged" in the mail merge process for gift acknowledgement letter. We have to go to the constituent's record and mark the gift "Not Acknowledged" to re-create the gift letter. We can only access the conditions for the conditional mail merge when there is a gift batch that has been committed but not posted.
It is very cumbersome to have to create letters in configuration and in RE Mail; it was be much appreciated if Blackbaud can find a way to use the same letter for batches (in RE Mail) and for constituent records (in Configuration).1 -
Janices Brown:
We get "No records meet specified criteria" for conditional mail merges that we have marked "Acknowledged" in the mail merge process for gift acknowledgement letter. We have to go to the constituent's record and mark the gift "Not Acknowledged" to re-create the gift letter. We can only access the conditions for the conditional mail merge when there is a gift batch that has been committed but not posted.
It is very cumbersome to have to create letters in configuration and in RE Mail; it was be much appreciated if Blackbaud can find a way to use the same letter for batches (in RE Mail) and for constituent records (in Configuration).When the letters have been acknowledged and the merge didn't complete, you can globally change the acknowledged to not acknowledged. In Admin, go under gifts and create a "New Change" , pull your batch in under selected records, and change the acknowledgement field.
0 -
i have to confess I am not sure where to begin with this solution...sounds like a logical answer but I don't have a clue...
I'll have to experiment. Unless someone can direct me to step by step...I can usually figure it out if I have direction.
Thank you0 -
Daniel Noga:
After chatting with Support, the consensus for us is that some parameters preventing this letter from pulling may have been changed from inside the Word Merge Wizard that cannot be changed from outside of it, and then the Mail template was saved. This sounds relevant in your case, Marcia, because our support rep specifically asked us if we were doing a Conditional merge after we sent him screenshots of all of the tabs in that Mail template, and the gift itself, and he found nothing amiss. I could not answer that question for him; Problematically, we can't go in and change said theoretical setting, or even see if the merge is Conditional, because the Wizard won't let us get that far. The best solution we have right now is to delete it and set up a new one from scratch.
It seems odd to me that this would be possible at all. We should not be able to irrevocably break a Mail template. Limiting parameters should always be available without having to actually execute a merge.Daniel, are you by chance getting just that the merge is freezing and not progressing? I had that happen and it turns out it was a compatability issue with a specific update to Word, that was causing the merge to hang. It was an easy fix, but I got the fix from my own research and support couldn't determine what the problem was, so I was then able to fix the conditional merge and move on from there.
0 -
I agree with the call for BB to have ONE place to enter letters. We never enter the whole letter in Config anymore because we don't run one-off letters from the gift - only with a batch in Mail. We only create the name in Config (though I don't understand why that is necessary) and then do the Wizard and the conditional merge in Mail.Then we have a conditional mail-merge for our batches and have no problems with it once it's set up. The "no records" thing is almost always because the gift is marked as acknowledged. We say "no" to the "Mark as Acknowleged?" screen the first time through - it's not unusual for us to have to redo the merge for some reason. After merging the letters and printing them off, we "run" the merge again just to the point of the "Mark as Acknowleged?" screen and say "yes" when we're sure we're done with that batch. The occassional one-off letter can be changed/copied/created in the saved Word letter batch from our shared drive and noted or copied to Media or an Action in RE.
As to the problem of the changes not being saved, I had that over and over and it drove me nuts, but I know how to fix that. After you've made a change to a conditional mail-merge letter, you MUST complete the merge all the way to the Word output, or the changes won't be saved. Don't "cancel" and go back and save at the first screen - it won't work. Name the merge something and send it somewhere you can find and delete it, THEN go back and save. I can't tell you how many times I typed in an entire letter, forgot to merge it, and had to start over again.
Aldera's experience with the freezing of the merge has happened every time we upgraded or set up a new computer. We refer to it as the "alt-ding" problem, becasue you have to use Alt-Tab to see the different open windows and find the error message that is buried somewhere (my computer said "ding" every time). For those experiencing this, it is a "Registry" problem and given the number of times it has come up, I think BB should finally train all its support folks on how to fix this. It is, as Aldera said, a fairly easy fix, but don't ask me how IT did it!0 -
I have the same problem as Marcia (Reed) in regards to updating the template within RE:Mail - and my formatting does not hold. I have done this so many times, even deleted and started from scratch - all to no avail. I have done everything recommended by Client Support - formatting of margins, fonts, etc on the first template in the series and follow suit with all remaining templates. I have given up at this point and I resort to control All and update to the font that I want. It's a total nuisance .
if anyone has a recommendation I am "all ears" :-)0 -
Just as a follow-up as I wasn't clear - I do run the conditional mail merge all the way through to final upload of the docs - multiple times all to the same effect - changes/updates not applied.0
-
I had that problem at first too - trying to piggy-back on an existing mail merge. Some of the margins were doubled and some disappeared, the font sizes kept changing - enough to make you scream. A temporary piece of voodoo that fixed it was to take the problem document and move it up the list to the top. I have no idea how this worked, but it did!
But really, the only way I've found to do it is to make sure your Word defaults (margins, font, font size, date format, etc.) are just as you want them outside of RE, start a new Mail Merge, and create and type (DON'T copy and paste!) all new letters. Every once in a while, they seem to just get corrupted. No point in going on - just start over. Fortunately (knock on wood) we've had one that has been working perfectly for a couple years now. If my boss makes really major changes to the letters in January, I'll probably start over rather than edit. I'm not looking forward to it, but it makes life easier in the long run.0 -
From what I've been able to tell from trial and error, all custom settings (margins, fonts, etc.) for a Word document are based on changes from the "Normal" template. If the "Normal" template gets changed then it has a cascading effect on all the other customizations you've made. When building documents for the Merge Wizard there is A LOT of potential for each of those conditional merge documents to have differing "Normal" styles and it results in chaos in the final merged document (that can even vary depending on which is the first "Normal" that gets pulled into the merged document).
Always start clean. Type each letter from scratch using the EXACT setup that will be used for the final merge (don't copy and paste ANYTHING). Learn how MERGEFORMAT and other field codes affect the merged document (https://support.office.com/en-in/article/Insert-and-format-field-codes-in-Word-2010-7e9ea3b4-83ec-4203-9e66-4efc027f2cf3) Sometimes something as simple as changing which printer is chosen during document creation can change font spacing, margins, etc. And remember, this isn't a typewriter. Use tabs and other formatting controls instead of multiple spaces (if you have to hit the space bar or Enter key more than twice in a row, you're probably doing it wrong!).0 -
I'm going to second John here. I had to start from scratch to get the formatting to remain fairly consistent. One thing I could never get to work and eventually gave up on was alternating footers. No matter what I did it seemed to want to use the same footer language for each letter even if there had been different language use on each different letter for the merge. It would leave the footer blank if that's what I told it to do, but not use text a, b, or c accordingly. It's was all a or blank.0
Categories
- All Categories
- Shannon parent
- shannon 2
- shannon 1
- 21 Advocacy DC Users Group
- 14 BBCRM PAG Discussions
- 89 High Education Program Advisory Group (HE PAG)
- 28 Luminate CRM DC Users Group
- 8 DC Luminate CRM Users Group
- Luminate PAG
- 5.9K Blackbaud Altru®
- 58 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 409 bbcon®
- 2.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- donorCentrics®
- 1.1K Blackbaud eTapestry®
- 2.8K Blackbaud Financial Edge NXT®
- 1.1K Blackbaud Grantmaking™
- 527 Education Management Solutions for Higher Education
- 1 JustGiving® from Blackbaud®
- 4.6K Education Management Solutions for K-12 Schools
- Blackbaud Luminate Online & Blackbaud TeamRaiser
- 16.4K Blackbaud Raiser's Edge NXT®
- 4.1K SKY Developer
- 547 ResearchPoint™
- 151 Blackbaud Tuition Management™
- 1 YourCause® from Blackbaud®
- 61 everydayhero
- 3 Campaign Ideas
- 58 General Discussion
- 115 Blackbaud ID
- 87 K-12 Blackbaud ID
- 6 Admin Console
- 949 Organizational Best Practices
- 353 The Tap (Just for Fun)
- 235 Blackbaud Community Feedback Forum
- 55 Admissions Event Management EAP
- 18 MobilePay Terminal + BBID Canada EAP
- 36 EAP for New Email Campaigns Experience in Blackbaud Luminate Online®
- 109 EAP for 360 Student Profile in Blackbaud Student Information System
- 41 EAP for Assessment Builder in Blackbaud Learning Management System™
- 9 Technical Preview for SKY API for Blackbaud CRM™ and Blackbaud Altru®
- 55 Community Advisory Group
- 46 Blackbaud Community Ideas
- 26 Blackbaud Community Challenges
- 7 Security Testing Forum
- 1.1K ARCHIVED FORUMS | Inactive and/or Completed EAPs
- 3 Blackbaud Staff Discussions
- 7.7K ARCHIVED FORUM CATEGORY [ID 304]
- 1 Blackbaud Partners Discussions
- 1 Blackbaud Giving Search™
- 35 EAP Student Assignment Details and Assignment Center
- 39 EAP Core - Roles and Tasks
- 59 Blackbaud Community All-Stars Discussions
- 20 Blackbaud Raiser's Edge NXT® Online Giving EAP
- Diocesan Blackbaud Raiser’s Edge NXT® User’s Group
- 2 Blackbaud Consultant’s Community
- 43 End of Term Grade Entry EAP
- 92 EAP for Query in Blackbaud Raiser's Edge NXT®
- 38 Standard Reports for Blackbaud Raiser's Edge NXT® EAP
- 12 Payments Assistant for Blackbaud Financial Edge NXT® EAP
- 6 Ask an All Star (Austen Brown)
- 8 Ask an All-Star Alex Wong (Blackbaud Raiser's Edge NXT®)
- 1 Ask an All-Star Alex Wong (Blackbaud Financial Edge NXT®)
- 6 Ask an All-Star (Christine Robertson)
- 21 Ask an Expert (Anthony Gallo)
- Blackbaud Francophone Group
- 22 Ask an Expert (David Springer)
- 4 Raiser's Edge NXT PowerUp Challenge #1 (Query)
- 6 Ask an All-Star Sunshine Reinken Watson and Carlene Johnson
- 4 Raiser's Edge NXT PowerUp Challenge: Events
- 14 Ask an All-Star (Elizabeth Johnson)
- 7 Ask an Expert (Stephen Churchill)
- 2025 ARCHIVED FORUM POSTS
- 322 ARCHIVED | Financial Edge® Tips and Tricks
- 164 ARCHIVED | Raiser's Edge® Blog
- 300 ARCHIVED | Raiser's Edge® Blog
- 441 ARCHIVED | Blackbaud Altru® Tips and Tricks
- 66 ARCHIVED | Blackbaud NetCommunity™ Blog
- 211 ARCHIVED | Blackbaud Target Analytics® Tips and Tricks
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- Luminate CRM DC Users Group
- 225 ARCHIVED | Blackbaud eTapestry® Tips and Tricks
- 1 Blackbaud eTapestry® Know How Blog
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)
- 1 Blackbaud K-12 Education Solutions™ Blog
- 280 ARCHIVED | Mixed Community Announcements
- 3 ARCHIVED | Blackbaud Corporations™ & Blackbaud Foundations™ Hosting Status
- 1 npEngage
- 24 ARCHIVED | K-12 Announcements
- 15 ARCHIVED | FIMS Host*Net Hosting Status
- 23 ARCHIVED | Blackbaud Outcomes & Online Applications (IGAM) Hosting Status
- 22 ARCHIVED | Blackbaud DonorCentral Hosting Status
- 14 ARCHIVED | Blackbaud Grantmaking™ UK Hosting Status
- 117 ARCHIVED | Blackbaud CRM™ and Blackbaud Internet Solutions™ Announcements
- 50 Blackbaud NetCommunity™ Blog
- 169 ARCHIVED | Blackbaud Grantmaking™ Tips and Tricks
- Advocacy DC Users Group
- 718 Community News
- Blackbaud Altru® Hosting Status
- 104 ARCHIVED | Member Spotlight
- 145 ARCHIVED | Hosting Blog
- 149 JustGiving® from Blackbaud® Blog
- 97 ARCHIVED | bbcon® Blogs
- 19 ARCHIVED | Blackbaud Luminate CRM™ Announcements
- 161 Luminate Advocacy News
- 187 Organizational Best Practices Blog
- 67 everydayhero Blog
- 52 Blackbaud SKY® Reporting Announcements
- 17 ARCHIVED | Blackbaud SKY® Reporting for K-12 Announcements
- 3 Luminate Online Product Advisory Group (LO PAG)
- 81 ARCHIVED | JustGiving® from Blackbaud® Tips and Tricks
- 1 ARCHIVED | K-12 Conference Blog
- Blackbaud Church Management™ Announcements
- ARCHIVED | Blackbaud Award Management™ and Blackbaud Stewardship Management™ Announcements
- 1 Blackbaud Peer-to-Peer Fundraising™, Powered by JustGiving® Blogs
- 39 Tips, Tricks, and Timesavers!
- 56 Blackbaud Church Management™ Resources
- 154 Blackbaud Church Management™ Announcements
- 1 ARCHIVED | Blackbaud Church Management™ Tips and Tricks
- 11 ARCHIVED | Blackbaud Higher Education Solutions™ Announcements
- 7 ARCHIVED | Blackbaud Guided Fundraising™ Blog
- 2 Blackbaud Fundraiser Performance Management™ Blog
- 9 Foundations Events and Content
- 14 ARCHIVED | Blog Posts
- 2 ARCHIVED | Blackbaud FIMS™ Announcement and Tips
- 59 Blackbaud Partner Announcements
- 10 ARCHIVED | Blackbaud Impact Edge™ EAP Blogs
- 1 Community Help Blogs
- Diocesan Blackbaud Raiser’s Edge NXT® Users' Group
- Blackbaud Consultant’s Community
- Blackbaud Francophone Group
- 1 BLOG ARCHIVE CATEGORY
- Blackbaud Community™ Discussions
- 8.3K Blackbaud Luminate Online® & Blackbaud TeamRaiser® Discussions
- 5.7K Jobs Board