<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Mail Merge - The Third Rail of Salesforce.com</title>
	<link>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/</link>
	<description>The Salesforce Heretic - Pushing the limits of On-Demand CRM</description>
	<pubDate>Tue, 06 Jan 2009 01:40:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Hobo Jojo</title>
		<link>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-4722</link>
		<pubDate>Tue, 28 Nov 2006 15:24:32 +0000</pubDate>
		<guid>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-4722</guid>
					<description>What happenned to the new word mail merge system? Don't see either heretic's code package or the Appexchange system.  An easy-to-use bulk mail merge is preventing us from acquiring salesforce.com.</description>
		<content:encoded><![CDATA[<p>What happenned to the new word mail merge system? Don&#8217;t see either heretic&#8217;s code package or the Appexchange system.  An easy-to-use bulk mail merge is preventing us from acquiring salesforce.com.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Salesforce Heretic &#187; Salesforce.com Mail Merge - Part IV:</title>
		<link>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-30</link>
		<pubDate>Tue, 25 Apr 2006 15:56:03 +0000</pubDate>
		<guid>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-30</guid>
					<description>[...] If you haven&#8217;t read them parts I, II, and III get into how were going to do the merge, as well as how we&#8217;re going to get the data. At this point we&#8217;ve settled on using the XML merge feed from the Salesforce.com UI, and we&#8217;re going to generate CSV data to get fed into Word. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] If you haven&#8217;t read them parts I, II, and III get into how were going to do the merge, as well as how we&#8217;re going to get the data. At this point we&#8217;ve settled on using the XML merge feed from the Salesforce.com UI, and we&#8217;re going to generate CSV data to get fed into Word. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Salesforce Heretic &#187; Salesforce.com Mail Merge, Part III: &#8220;Spaulding, this calls for the ole Billy Barule&#8230;&#8221;</title>
		<link>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-22</link>
		<pubDate>Fri, 21 Apr 2006 16:30:45 +0000</pubDate>
		<guid>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-22</guid>
					<description>[...] So, in a quick recap, we&#8217;ve already laid down, in general terms anyway, why we&#8217;re doing this, and generally how we&#8217;re going to do the merge. Now it&#8217;s time to get the data. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] So, in a quick recap, we&#8217;ve already laid down, in general terms anyway, why we&#8217;re doing this, and generally how we&#8217;re going to do the merge. Now it&#8217;s time to get the data. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eugene Chan</title>
		<link>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-18</link>
		<pubDate>Tue, 18 Apr 2006 19:49:37 +0000</pubDate>
		<guid>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-18</guid>
					<description>This is probably THE biggest downside to Salesforce that I can that is/will be a point of pain for day to day users. 

Very cool that they are addressing the issue.

Thanks for the post!</description>
		<content:encoded><![CDATA[<p>This is probably THE biggest downside to Salesforce that I can that is/will be a point of pain for day to day users. </p>
<p>Very cool that they are addressing the issue.</p>
<p>Thanks for the post!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: gokubi.com &#187; Blog Archive &#187; New mail merge facility coming soon in Appexchange&#8230;</title>
		<link>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-17</link>
		<pubDate>Tue, 18 Apr 2006 19:06:50 +0000</pubDate>
		<guid>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-17</guid>
					<description>[...] In a comment today on a post about Word mail merge in Salesforce.com over at Salesforce Heretic, it was announced that Salesforce.com is releasing a new mail merge system via the Appexchange in the next few days. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] In a comment today on a post about Word mail merge in Salesforce.com over at Salesforce Heretic, it was announced that Salesforce.com is releasing a new mail merge system via the Appexchange in the next few days. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Salesforce Heretic &#187; Salesforce.com Mail Marge, Part II: &#8220;Word made me do it&#8230;&#8221;</title>
		<link>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-15</link>
		<pubDate>Tue, 18 Apr 2006 17:48:17 +0000</pubDate>
		<guid>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-15</guid>
					<description>[...] Back in our introduction to this series, I elaborated on some of the issues surronding Mail Merges in Salesforce.com. In this part we&#8217;re going to look at how Word handles a Mail Merge, and figure out how we&#8217;ll get our data ready to be merged. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Back in our introduction to this series, I elaborated on some of the issues surronding Mail Merges in Salesforce.com. In this part we&#8217;re going to look at how Word handles a Mail Merge, and figure out how we&#8217;ll get our data ready to be merged. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Chris Hopkins</title>
		<link>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-14</link>
		<pubDate>Tue, 18 Apr 2006 17:28:57 +0000</pubDate>
		<guid>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-14</guid>
					<description>In the defense of mail merge:

When it was written (over 3 years ago, which is saying something as it has never been patched until now and there are over 15 thousand HAPPY customers using it) we had to EXACTLY duplicate the results generated by a now defunct company called hotpaper.  Maybe not a great decision but there it is.

Supporting conditional merge field logic was not considered (Iâ€™m really surprised it works at all).
We also wanted to support a basic quoting system (opportunity stuff mentioned above) which, while not impossible using a native merge, would still require modifying the word doc at runtime.

So to do that, I wrote a search and replace system that walks the document and swaps in the values.  
So no native merge ï?Œ

That said, the code that is going into production this week has a plugin system that allows people (like this gent) to swap out the standard search and replace component with their own component (perhaps one that simply runs the native word merge).
You can also swap out the data generation bit.

The new code is also scriptable, so it can be used in a scontrol to generate bulk results.  
This will be available in AppExchange soon as something you can go and install.


Now as far as back end merge goes I wish you luck using open office etc.  People have tried and failed to even get good support for ONE version of Office, let alone Office 2000 and up.
I also wish you luck running Word on the back end to generate results (which is NOT recommended by MS and is what hotpaper did, and where are they?).


NOTE: The problems with mail merge lately are related to the new production network stack dropping connections in a very unfriendly way.  
Our network guys are a bit baffled but since I have v 2 in the pipe (which has an upgraded network layer) we are more focused on getting that out the door, which will be this Friday (there is your timeline).</description>
		<content:encoded><![CDATA[<p>In the defense of mail merge:</p>
<p>When it was written (over 3 years ago, which is saying something as it has never been patched until now and there are over 15 thousand HAPPY customers using it) we had to EXACTLY duplicate the results generated by a now defunct company called hotpaper.  Maybe not a great decision but there it is.</p>
<p>Supporting conditional merge field logic was not considered (Iâ€™m really surprised it works at all).<br />
We also wanted to support a basic quoting system (opportunity stuff mentioned above) which, while not impossible using a native merge, would still require modifying the word doc at runtime.</p>
<p>So to do that, I wrote a search and replace system that walks the document and swaps in the values.<br />
So no native merge ï?Œ</p>
<p>That said, the code that is going into production this week has a plugin system that allows people (like this gent) to swap out the standard search and replace component with their own component (perhaps one that simply runs the native word merge).<br />
You can also swap out the data generation bit.</p>
<p>The new code is also scriptable, so it can be used in a scontrol to generate bulk results.<br />
This will be available in AppExchange soon as something you can go and install.</p>
<p>Now as far as back end merge goes I wish you luck using open office etc.  People have tried and failed to even get good support for ONE version of Office, let alone Office 2000 and up.<br />
I also wish you luck running Word on the back end to generate results (which is NOT recommended by MS and is what hotpaper did, and where are they?).</p>
<p>NOTE: The problems with mail merge lately are related to the new production network stack dropping connections in a very unfriendly way.<br />
Our network guys are a bit baffled but since I have v 2 in the pipe (which has an upgraded network layer) we are more focused on getting that out the door, which will be this Friday (there is your timeline).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jubub</title>
		<link>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-12</link>
		<pubDate>Tue, 18 Apr 2006 09:21:51 +0000</pubDate>
		<guid>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-12</guid>
					<description>IÂ´m a german user, so please excuse my english...
I still fight with the conditional issue, too! We tried to work around this using Excel sheets within the Word application. Only then, describing what to do when no data is written in the required field we were able to "kill" the description in that line and also the empty line itself. For example: I donÂ´t want Word to write "discount" when that special account gets no discount at all! It would be much easier and close to the original concept to get along using Word only... SomeoneÂ´s got an idea?</description>
		<content:encoded><![CDATA[<p>IÂ´m a german user, so please excuse my english&#8230;<br />
I still fight with the conditional issue, too! We tried to work around this using Excel sheets within the Word application. Only then, describing what to do when no data is written in the required field we were able to &#8220;kill&#8221; the description in that line and also the empty line itself. For example: I donÂ´t want Word to write &#8220;discount&#8221; when that special account gets no discount at all! It would be much easier and close to the original concept to get along using Word only&#8230; SomeoneÂ´s got an idea?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jaded</title>
		<link>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-11</link>
		<pubDate>Fri, 14 Apr 2006 23:59:01 +0000</pubDate>
		<guid>http://sfdc-heretic.warped-minds.com/2006/04/14/mail-merge-the-third-rail-of-salesforcecom/#comment-11</guid>
					<description>Actually I can't even get mail merge to work right now with documents that exeucuted perfectly a few weeks ago.  Salesforce is having serious issues with it and isn't releasing a timeline for these to be fixed.</description>
		<content:encoded><![CDATA[<p>Actually I can&#8217;t even get mail merge to work right now with documents that exeucuted perfectly a few weeks ago.  Salesforce is having serious issues with it and isn&#8217;t releasing a timeline for these to be fixed.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
