The Connector doesn't use the standard CRM merge functionality, but something outside of it. I'm not sure it can be configured to save the document in the Documents tab (and a communication along with it).

Ok thanks. But can it be configured to merge to word as there is usually a requirement to edit the merged document before sending.

I would recommend that you speak with the UK Product Management team for Sage 200 and make a feature change request for the Mail Merge.

I don't know if I'm holding the wrong end of the stick here, but if I change one line of Print.asp to read:

merger.doPdf = false;

...then it does exactly what it threatens to do - i.e. merge to a .doc file as opposed to a .pdf.

Chris

Is this the original merge method or the new one? Which version of the connector?

I see that line in the Sage300 print.asp but in the sage200 print.asp this is what we have on v3.1

<%

Server.ScriptTimeout = 180;

var sTemplate = "";

var sTable = "";

switch ((new String(Request.QueryString("type")).toLowerCase())){

case "quote":

//sTemplate = "quotetemplate.doc";

sTemplate = "PrintQuoteTemplate.docx";

sTable = "S200SOPQuote";

break;

case "order":

//sTemplate = "ordertemplate.doc";

sTemplate = "PrintOrderTemplate.docx";

sTable = "S200SOPOrder";

break;

}

var sS200CompanyId = eWare.GetContextInfo("Company", "comp_s200_companyId");

var s200DocumentId = Request.QueryString("documentno");

var sType = Request.QueryString("type");

var sMergerURl = eWare.URL(565)+ "&Mode=3type=" + sType + "&Sage200MailMerge=Y&Sage200Template=" + sTemplate + "&Sage200CompanyId=" + sS200CompanyId + "&Sage200DocumentId=" + s200DocumentId + "&Sage200TableName=" + sTable;

if (sTemplate!="" && sTable!="") Response.Redirect(sMergerURl);

%>

You know what? Them's the perils of multiple virtual machines. I was looking at an older version of Connector.

I wonder how this works now then? Might have to dismantle it a bit.