{"id":3287,"date":"2013-05-06T14:33:28","date_gmt":"2013-05-06T09:03:28","guid":{"rendered":"http:\/\/JitendraZaa.com\/blog\/?p=3287"},"modified":"2013-05-06T14:33:28","modified_gmt":"2013-05-06T09:03:28","slug":"extended-mail-merge-template","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/extended-mail-merge-template\/","title":{"rendered":"Extended Mail Merge Template"},"content":{"rendered":"

In many cases, I have seen customer struggling with “Standard Mail Merge”\u009d functionality. I have suggested them to either use “Drawloop<\/a>“\u009d or “Conga Composer<\/a>“\u009d however these applications are paid.<\/p>\n

Before going ahead let’s see the drawbacks of “Standard Mail Merge”\u009d:<\/strong><\/p>\n

    \n
  1. It runs on Client side and needs ActiveX Control<\/li>\n
  2. It needs Internet Explorer<\/li>\n
  3. It does not work with Office 2010, it works only for Office 2003 and 2007<\/li>\n
  4. Windows 7 is not supported and causes unexpected error many times. It supports Windows XP and Windows Vista only<\/li>\n<\/ol>\n

    The solutions to all above problem is “Extended Mail Merge (XMM)”\u009d template which is free and native Salesforce solution.<\/p>\n

    Following are the advantages of “Extended Mail Merge (XMM)”\u009d:<\/strong><\/p>\n

      \n
    1. It runs on server side and does not require installation of any ActiveX Control<\/li>\n
    2. It runs on almost al major browsers including firefox, Chrome<\/li>\n
    3. It supportes Office 2007 as well as Office 2010 (document must be saved in a 97-2003 DOC format)<\/li>\n
    4. We can save output into “Document”\u009d tab<\/li>\n
    5. XMM can send final word document in email itself<\/li>\n<\/ol>\n

      NOTE: <\/strong>Mail Merge & Extended Mail Merge uses same templates: “Setup | Communications Templates | Mail Merge Templates”<\/p>\n

      There are few limitations in XMM also like:<\/strong><\/p>\n

        \n
      1. At a time, it can merge only 1000 records.<\/li>\n
      2. Template size cannot exceed 1MB of size.<\/li>\n
      3. It will access only those\u00a0fields\u00a0for which current user have access, it respects Field level security (FLS)<\/li>\n<\/ol>\n

        How to enable “Extended Mail Merge (XMM)”\u009d ?<\/strong>
        \nWe have to contact Salesforce to enable this feature in our Salesforce Organization.<\/p>\n

        How to activate “Extended Mail Merge (XMM)”\u009d , once it is enabled by Salesforce?<\/strong>
        \nNavigate to “Setup | Customize | User Interface”\u009d and select checkbox “Activate Extended Mail Merge”\u009d. We can also select to save XMM result in Document tab as shown in below snap.<\/p>\n

        \"Insert<\/a>
        Insert Field in Extended Mail Merge Salesforce<\/figcaption><\/figure>\n
        \"Activate<\/a>
        Activate Extended Mail Merge – User Interface – Salesforce<\/figcaption><\/figure>\n

        Before using XMM , we have to create template in Microsoft Word. So, lets see how to create template.<\/p>\n

        For this article, let’s say our template is going to be used by “Contact”\u009d object and content should be as simple as :<\/p>\n

        \nHello \u00abContact_FirstName\u00bb,\nPhone Number - \u00abContact_Phone\u00bb\nRegards\nShivasoft\n<\/pre>\n
        In above paragraph, “CONTACT_Name”\u009d needs to be replaced by actual contact name. For this, we need API name of that field from Salesforce which is “Name”\u009d. Now create above template in Microsoft word and place the cursor where we want value to be appeared and navigate to “Insert | Quick Parts | Fields”\u009d.<\/p>\n
        \"Insert<\/a>
        Insert Field in Extended Mail Merge Salesforce<\/figcaption><\/figure>\n
        New window will appear, select MergeField and enter API Name as shown in below image.<\/p>\n
        Note :<\/strong> <\/span>While entering API name of any field, It should be prefixed by Object name and\u00a0Underscore\u00a0 . For Example, API Name in Contact Should be referred as Contact_Name. (Object_FieldAPIName<\/strong>) .<\/p>\n
        \"Insert<\/a>
        Insert Field in Template – Salesforce<\/figcaption><\/figure>\n
        Now, go to Salesforce and navigate to “Set up | Communication Templates | Mail Merge Templates”\u009d and Upload recently created template.<\/p>\n
        Now to check that whether template is working or not. Navigate to Contact Tab and select “Mass Mail Merge”\u009d link present at bottom.<\/p>\n
        Step 1:<\/strong>
        \nSelect List of Contacts for which you want to run “Mail Merge”\u009d template.<\/p>\n
        Step 2:<\/strong>
        \nSelect Document Types to Generate. The Supported document types are documents, envelopes and labels. You can also select if you want to Log an activity that mail merge documents were generated for those records.<\/p>\n
        Step 3:<\/strong>
        \nSelect Document templates to be used by “Mass Mail Merge”\u009d which we have created in this article. In this step we can select that all documents to be generated in single word document or we have to create separate word files.
        \nOnce we click on finish button, we will get messag that email will be sent to email id once document is generated.<\/p>\n
        \"Extended<\/a>
        Extended Mail Merge – XMM Confirmation Window<\/figcaption><\/figure>\n
        Point to Remember:<\/strong><\/p>\n
          \n
        • Prefix the field label with the type of record. For example, “Account_MarketCap”\u009d for an account field named MarketCap.<\/li>\n
        • Convert all spaces to underscores. For example, a custom opportunity field named “Product ID”\u009d becomes “Opportunity_Product_ID”\u009d.<\/li>\n<\/ul>\n
          References:<\/strong>
          \n          Mail Merge Documentation<\/a><\/p>\n
          Read more about using Merge Fields in Mail Merge here<\/a><\/p>\n