Conditional Mail Merge refuses to recognize valid file paths. Anyone else?

Options

This change to outside word merge has been a project from hades. I knew it would be tedious, but I had no idea how incredibly tedious. I am having a great deal of difficulty getting word merge to recognize file paths to my documents with the conditional list (the one where it finds a letter and uses that) I will finally get it working with one, then the next one won't work for no obvious reason. The paths look exactly the same. I know about making sure its double slashes. I know you have to start every cotton picking IF/THEN statement from scratch and that it refuses to recognize any kind of copying and pasting of the Merge parameters/rules. I have finally been able to coax it to accept some of the file paths as copy and paste because I cannot type all those in by hand. There just seems to be no consistency. Has anyone else had this much trouble? Advice appreciated. I have looked at some of the other boards covering the mail merge chaos and have not found this particular issue. Thanks!

Tagged:

Comments

  • Dariel Dixon 2
    Dariel Dixon 2 ✭✭✭✭✭
    Seventh Anniversary Facilitator 4 Name Dropper Photogenic

    Did you create your letter path document? We have a text file that defines every path for each letter template we have. And we have at least 15 different letter templates. It's a chore no doubt, but it can be done. I'm sure you will be able to get through it.

    I think the best route to go is to create the master document by saving often, and adding them one by one once you get them loaded correctly.

  • Austen Brown
    Austen Brown ✭✭✭✭✭
    Ninth Anniversary Facilitator 4 Name Dropper Photogenic

    @Sandra Moore - Would you be willing to share a screenshot of your Master Merge Document? We may be able to help more if we can see how your file paths are entered.

  • Thanks Dariel. That “one by one” thing is a killer, isn't it. I appreciate the cheering on. I'm a patient person but this is testing me…….your situation sounds very similar to ours.

  • Dariel Dixon 2
    Dariel Dixon 2 ✭✭✭✭✭
    Seventh Anniversary Facilitator 4 Name Dropper Photogenic

    Sandra Moore:

    Thanks Dariel. That “one by one” thing is a killer, isn't it. I appreciate the cheering on. I'm a patient person but this is testing me…….your situation sounds very similar to ours.

    @Sandra Moore You'll get through this Sandra. I have faith in you, as well as everyone going through this (and we are all going through it). You'll get it done, and have a great sense of accomplishment afterward.

    If I had hair, I would have definitely pulled it out over this situation. I personally think we should all have a party after March once we get our processed documented and tightened up. You're all invited.

  • Austen Brown:

    @Sandra Moore - Would you be willing to share a screenshot of your Master Merge Document? We may be able to help more if we can see how your file paths are entered.

    Austen, here is the actual code. The first three work fine, the fourth does not (highlighted in grey), although I copied the path directly from the system (shift right click on file name and chose “copy path”) then added the additional slash just as I did for the others. I created the whole statement from scratch - no copying and pasting other than the initial file path, which is what I did for the ones that work too. I see no logical explanation for why it says that file name is invalid. But, maybe this project has made me completely bleary eyed. I thought I would be done but it just takes so long when you hit issues like this.

    I included the return marks too so you can see that it is not because I have any hard returns.

    Thanks!

    540f996fa1d4b45df62e9780f35e73bc-huge-im

  • Dariel Dixon:

    @Sandra Moore You'll get through this Sandra. I have faith in you, as well as everyone going through this (and we are all going through it). You'll get it done, and have a great sense of accomplishment afterward.

    If I had hair, I would have definitely pulled it out over this situation. I personally think we should all have a party after March once we get our processed documented and tightened up. You're all invited.

    Amen to that! If there is ever another in-person Blackbaud conference, BB owes us a spectacular one for this!

  • In your Care for Caregivers code, there is a space after the Caregivers.doc in the INCLUDETEXT parameter

    That caused one of mine not to work.

  • Found it: In your version highlighted grey, there is only a single \\ before the word Reports. It needs to be a double \\\\

  • Austen and Dariel, you both, and my coworkers who are worried about me walking around looking wild eyed, will be happy to know that I found the problem. That always happens when we finally reach out for help, right? I call it the Murphy's Law of Helpdesk. Anyway, the problem was when I was editing the mergefield I was not putting the path in the tiny box shown in the print screen here, up above “format”. I never noticed it until just a few minutes ago. I went back and looked at the instructions and it is obvious this is what they did, but it is very light grey and doesn't really jump out. When I do this the code actually comes out with the slashes already in place AND - this is big - an extra “\\ before the path name. I was copying in the path after I had the Mergefield {INCLUDETEXT } already set up.

    In my defense though, as can be seen from my code snippet, it works without that extra quote and slash for my first three letters. Had nothing worked I probably would have gone on a search earlier, but when something works and replicating it doesn't, you finally throw up your hands like I did.

    I will use that url box from here on out, and update the ones I did that worked to fit the format so they don't break in the future. Hopefully this will come in handy for someone else too.

    Thanks for your input. Have a great day! - Sandra

    534f03561b5616c33e79e4c5ed973a23-huge-im
  • Jennifer Warner:

    Found it: In your version highlighted grey, there is only a single \\ before the word Reports. It needs to be a double \\\\

    Ah, thank you, Jennifer, for taking the time to look at that. I knew there had to be some reason, but despite the fact I had looked at it multiple times, I still missed it. I was very bleary eyed by that time. The organization I am doing this for has a large number conditional acknowledgments covering a wide array of possibilities (Hospital Foundations are often like this due to the numerous service lines that the funds support) and we need to build three of these conditional statement documents. Fresh eyes, fresh perspective - that is why it is always a good idea to step away when we find ourselves stuck! Thanks too for your point about the space.

    This also drives home the importance of using the direct copy of path to direct paste into the URL box above in the properties area of the INCLUDETEXT command. When one tiny slash can make all the difference, even minimal hand editing like adding the slashes can be dangerous. I wish that piece was highlighted more on the instructions BB provided, though I have seen no other posts of someone having this particular problem, so maybe I'm the only one who missed it. Anyway, better late than never. I expect this project to move along at a pretty fast clip now.

    Note - I also have begun using the option of “updating field” by right clicking within the brackets if I do any sort of hand editing of something within a merge field. Though I can't say for certain it makes a difference, because I don't see anything change when I do it, I also have stopped having errors.

    Great project for professional development…….(trying to find the silver lining here.)

    I just looked at your profile. You work in Healthcare too! You know all about many service lines/many funds then! ?

  • Sandra,

    I am so grateful you posted! I am having the exact same issue right now. I am just starting this process after having watched the Youtube video several times and it got me started but that was all. I just started my job as Database Manager about two weeks ago and got thrown into the fire immediately.

    I looked at your screen shot and it looks different than mine. Do you name all your templates with the extension? Mine seems to have an extra field called Merge Format that you don't have. Now I am really confused…

    2a790cc07b6992f02bab999ff1eb4871-huge-co
  • Mary Ellen Cenzalli:

    Sandra,

    I am so grateful you posted! I am having the exact same issue right now. I am just starting this process after having watched the Youtube video several times and it got me started but that was all. I just started my job as Database Manager about two weeks ago and got thrown into the fire immediately.

    I looked at your screen shot and it looks different than mine. Do you name all your templates with the extension? Mine seems to have an extra field called Merge Format that you don't have. Now I am really confused…

    2a790cc07b6992f02bab999ff1eb4871-huge-co

    Oh good! I'm so glad my missed slash crisis is of help to others. Helps make up for my feeling kind of stupid for missing it! ?

    The MERGEFORMAT thing is optional. When you are in the area of the field edit I showed in my printscreen, to the right of it are other options. At the bottom is a checkbox that talks about retaining formatting - if its checked you get the additional “MERGEFORMAT”, if unchecked it looks like mine. We decided to not include this to keep things simple. I really do not know the impact one way or the other, but it does not seem to have hurt anything to keep it off and these commands are going to be plenty tedious to edit if ever needed as is. Also, see the discussion about it here

    Wow - two weeks as a DB manager and this is handed to you. My heart goes out to you. On the bright side, now that I finally understand how to make this work, I will say that I have learned a lot about word merge, and am curious to see what else can be done with some of those commands in the field edit list. Professional Development, right?

Categories