You're not going to master the rest of your life in one day. Just relax. Master the day. Than just keep
Idea Transcript
Aust 1800 362 254 | NZ 0800 362 254
Home
Solutions
Services
Products
Raving Fans
Resources
About Us
Events
Blog
Contact Us
Home › Blog › How Mail Merge Works
By Guest Blogger Jeff Richards | SAGE In this article I want to discuss how the Mail Merge process works in detail. This includes what happens within Sage CRM and how the document is created. The Mail Merge mechanism changed in Sage CRM v7.1sp2. If need to know how Mail Merge used to work then see the article "How Mail Merge Works in Sage CRM v7.1 SP1 and earlier." Mail Merge for Sage CRM v7.1sp2 onwards takes place server side. I have discussed previously in the article "System Architecture" how Sage CRM's design is undergoing a process of change.
Tweets by @Enabling_net Load new Tweets Enabling Retweeted SAP Analytics @SAPAnalytics 5 trends creating opportunities for businesses of all sizes @P_Miskiewicz What's at the core of digital business
Aug 1, 2016
Share on Twitter Facebook LinkedIn Tumblr
Sage CRM is moving more and more of its features into the java based technologies. Mail Merge is just one of the features that have been changed to work as a server side process under the Tomcat/Java processes. It is important to realise that because the merge takes place on the server that no text file or cookie is created during the new Mail Merge process and application data is not passed to the client. The old mechanism prior to Sage CRM 7.1 sp2 used to create files like "ewaremerge0.dat" and "ewareQuote0.dat" but these files are NEVER created now. There have been some very helpful articles written that explain how the Mail Merge works in the new technology.
Enabling @Enabling_net Analyzing Henrik Stenson's Recent Golf Success global.qlik.com/us/blog/posts/… via @msaliter #EnablingQlikAcademy eventbrite.com.au/e/enabling-qli… Jul 28, 2016
Share on
Mail Merge Changes in Sage CRM v7.1SP2 This article looks at the reasons for the change the advantages that it brings. It also very usefully discusses continuing to edit Word templates and insert fields into those documents. Editing an Existing Microsoft Word Mail Merge Template in Sage CRM The serverside merge uses HTML templates but can continue to use Word templates. This article discusses how system administrators can continue to maintain templates created in Word. Working with existing Microsoft Word mail merge templates in Sage CRM v7.1 SP2
Twitter Facebook LinkedIn Tumblr Enabling @Enabling_net Have you registered? "Enabling Qlik Academy | WA" eventbrite.com.au/e/enabling-qli… via @Eventbrite
This discusses how Word templates can be switched to HTML. Working with Microsoft Word Templates in Sage CRM Cloud 2012 R2 This article contains details of working with Quote or Order Microsoft Word Templates within the new architecture and looks at how labels can be printed. Data Sources Whether the server-side mail merge uses an HTML template or a Word template the data for the merge needs to be drawn from an underlying view. The view will changing according to the context in which the mail merge is initiated.
Jul 27, 2016
Share on Twitter Facebook LinkedIn Tumblr Embed
View on Twitter
The merge templates are stored in the Administration area Administration -> E-mail and Documents -> Document Templates As I have mention above Sage CRM now supports 2 types of templates for the merge process. HTML Templates Classic Sage CRM Word Templates HTML Templates can be saved as files before being uploaded into Document Templates. HTML extensions are allowed Templatename.html Templatename.htm Template for Quotes & Orders must be saved of correct Type Quote Order
Note: If your system uses a network share for mail merge templates then you will need to manually copy the new files to the network share. All users can create their own private templates and the process of creating a new template can be easily started by starting to perform a mail merge. Below you can see that a new HTML Template has started to be created.
You just need to start the mail merge process and opt to create a new template. The template will then be available in the context where created. The context determines the views that used and the fields that can be added to the template.
The following views are used Context Company - vMailMergeCompany Person - vMailMerge Opportunity - vMailMergeOpportunity Case - vMailMergeCase Lead - vListLead The Orders & Quotes are different as the merge process allows for header and detail merges to take place using information from two separate views. Quotes use vMailMergeQuotes and vMailMergeChildrenQuotes Orders use vMailMergeOrders and vMailMergeChildrenOrders vMailMergeChildrenQuotes CREATE VIEW vMailMergeChildrenQuotes AS SELECT QuoteItems.*, NewProduct.* FROM QuoteItems Left Outer Join NewProduct ON QuIt_ProductId = Prod_ProductId WHERE Quit_Deleted IS NULL vMailMergeChildrenOrders CREATE VIEW vMailMergeChildrenOrders AS SELECT OrderItems.*, NewProduct.* FROM OrderItems Left Outer Join NewProduct ON OrIt_ProductId = Prod_ProductId WHERE Orit_Deleted IS NULL
The process of creating HTML Quote or Merge templates requires you to insert special nested regions into the HTML of the template.
You can start the template using "Insert Nested Region". It is strongly recommended that you include the child information from the Order Items or the Quote Items with the structure of a table.
You should include the CID field beside each currency field. E.g «orIt_quotedprice_CID» «OrIt_quotedprice» as this will ensure correct formatting of the currency information. For more information, contact Enabling.
Business Intelligence Solutions Cemetery Management Software Cloud Solutions Construction and Project Management Software Customer Relationship Management EDI Solutions ERP Systems - Enterprise Resource Planning Financial Management Software Information Media and Telecommunications Manufacturing Software Mining Software Professional Services Retail POS Software Supply Chain Management Warehouse Management
IBM Cognos TM1 Info-Explorer Microsoft Dynamics CRM Microsoft Dynamics NAV On Center Estimating Software Orchid Product Suite PowerOLAP ProjectPro - Dynamics NAV Construction Projects for Sage 300 QlikView Product Family SAP Business One Sage 300 Sage 300 Construction and Real Estate Sage CRM Sage CRM Cloud Sage X3
Resources for Microsoft, Sage, SAP Business One and more...
About Us Awards & Recognition Blog Careers Contact Us Events News Privacy Policy
Success Stories from our customers
Business Analysis Business Consulting Cloud Services & SaaS to Managed Services Development Project Management Solution Consulting Technical Consulting