Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

I generate certificates of test data, up to 700 at a time, by merging a hand created form (document, template) with data in a spread sheet. I don't use the wizard. Once the form is done I swap out spread sheets (change data source) with each new set of data. For SF they state they need a .doc template and I don't know if the LO form for a merge translates to a .doc. Someone else may know. I pretty much follow the steps that have been described in this list, so possibly trying to merge with a spread sheet may be a first step before trying to create a template for SF. Create your list of data first, then make the form. Put a heading row at the top of each column to help.

On 2013-08-23 14:33, Carl Paulsen wrote:
Yes, that's the way I was working at this. But I realize there may be other approaches. Still, it made me wonder about hand-generating mail merge documents even without Salesforce, which is also something I'd like to understand how to do.

I occasionally get questions about spreadsheets, text documents, mail merges and the like, and where possible I extol the virtues of LO (I personally don't use MSO but may end up needing to if I can't figure out the mail merge/Salesforce issue). So any learning I can do on mail merges will help me be more convincing.

I also act as a consultant to non-profits for Salesforce and simple mail merges are a key concern. Salesforce has it's own weaknesses in that realm, but it's what I/we are stuck with. I'm working on learning all I can about it so I can speak with authority on more than just MSO.


On 8/22/13 10:21 PM, Steve Edmonds wrote:
Are you wanting to upload this document as a template for a SF extended mail merge. Do you need this document in .doc format (seems so from my quick look at SF instructions).

On 2013-08-23 13:48, Carl Paulsen wrote:
Thanks, Paul.  I've been away for a bit.

There is a LO connector for SF, but AFAIK that connector won't make a merge document work within the broader platform. But this may be worth looking into further. I'm still stuck on creating the document with next record and next page fields to make it actually function as a merge document.


On 8/15/13 10:29 AM, Paul D. Mirowsky wrote:
I am not an expert, but I do have a question.

Does "Salesforce" have a database connector that will allow you to use LibreOffice Base as an intermediary to your Writer document?


On 8/14/2013 1:35 PM, Carl Paulsen wrote:
I'm trying to create mail merge documents that contain merge fields for a document that can't connect directly to the data source. That source (Salesforce) can read the documents if the field names are correctly entered. I can type the field names in manually, but I can't figure out how to generate a label merge document that will work.

The mail merge wizard doesn't seemingly allow users to generate label merges (options are letter and email). And I can't find a way to generate a merge document manually without using the wizard. I see no menu items for mail merge steps (I can find the insert field tool, but that's it - no tool to allow me to switch between merge fields and merged data without going into the wizard).

I've tried starting with New->Labels, then choosing the correct label type and clicking New Document (I can't connect to the database, so can't enter the merge fields in the dialog). I can then type in merge fields as Salesforce wants to see them, but I can't figure out how to make it a merge document with the "next record" and "next page" items. In Insert->Fields there is a Next Record option but it's only available when there's a database connected.

Finally, I've been through a lot of documentation so if there's a good mail merge document online, that might be enough.

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.