#MICROSOFT DYNAMICS ONE DOC MERGE HOW TO#

NumberDecTotal := NumberDecTotal + NumberDec XMLNodeList2 := lectNodes(‘Line/Amount’) įOR j := 0 TO XMLNodeList2.length – 1 DO BEGIN Once you have the XMLNodeList, then you can go through the nodes in that list, using the first example.įinally, an example which will read the XML document shown above, and show an Amount-total for each order:įOR i := 0 TO XMLNodeList.length – 1 DO BEGIN

Note that the tag name you specify is case sensitive (like everything else in XML)! So in this case, it would not find elements called “order”. This will open the XML document, then use the getElementsByTagName-function to get all elements that match the tag name. MESSAGE(‘The document has %1 elements called Order’,XMLNodeList.length)

XMLNodeList := XMLDoc.getElementsByTagName(‘Document/Order’) So you do not have to read a document from top to bottom if you know exactly which parts of the document you are interested in.įirst, we can count how many orders the document contains (see how many “Order”-elements are under the root-element): One of the good things in MSXML DOM is, that it reads the whole document into memory, so you can jump between nodes, and browse them, and select sub-sets based on node names. Now, lets say you are looking for specific nodes in an XML document. This codeunit can be used for scanning any XML document from begin to end. Now, try to run the codeunit against any XML document, and it will give a MESSAGE for each node and each attribute. MESSAGE(CurrentElementName + ‘ = ‘ + FORMAT(CurrentXMLNode.nodeValue)) MESSAGE(CurrentElementName + ‘ Attribute : ‘ +įORMAT(CurrentXMLNode.nodeName) + ‘ = ‘ + FORMAT(CurrentXMLNode.nodeValue)) TempXMLNodeList := CurrentXMLNode.childNodes įOR j := 0 TO TempXMLNodeList.length – 1 DO TempXMLAttributeList := CurrentXMLNode.attributes įOR k := 0 TO TempXMLAttributeList.length – 1 DO If the element has attributes, then browse through those. Global variable CurrentElementName to keep track of what nodeĬurrentElementName := CurrentXMLNode.nodeName ReadChildNodes(CurrentXMLNode : Automation “‘Microsoft XML, v4.0’.IXMLDOMNode”) See the documentation (included in MSXMLSDK) for a complete list of possible nodeTypes. A node can be an element, text (data), attribute etc. The function checks to see what type of node it was called with. TempXMLAttributeList Automation = ‘Microsoft XML, v4.0’.IXMLDOMNamedNodeMap TempXMLNodeList Automation = ‘Microsoft XML, v4.0’.IXMLDOMNodeList And there can easily be a child node inside of another child node.ĬurrentXMLNode : Automation “‘Microsoft XML, v4.0’.IXMLDOMNode” This is useful because you don’t know how many child nodes there are. The reason for the functionis to enable you to run it recursively. You also have to create ReadChildNodes as a function with one parameter:ĬurrentXMLNode, Type = Automation ‘Microsoft XML, v4.0’.IXMLDOMNode. Set up a loop to browse through the nodes in the document:įor i := 0 to XMLNodeList.length – 1 do begin XMLNodeList Type = Automation ‘Microsoft XML, v4.0’.IXMLDOMNodeListĤ. XMLDoc Type = Automation ‘Microsoft XML, v4.0’.DOMDocumentĭOMNode Type = Automation ‘Microsoft XML, v4.0’.IXMLDOMNode This is how you can read an XML Document from Microsoft Dynamics NAV, using MSXML DOM: So even if you only want to read XML Documents, then you may want to have a look there anyway.īut let’s get straight to the point. The other post conitains a few more background details which I won’t repeat here.

#MICROSOFT DYNAMICS ONE DOC MERGE HOW TO#

We are using Outlook 2007 to use CRM to send these emails out.This is a follow-up to the post “ how to write a simple XML document“. We are using the unsubscribe link option. We are tracking responses (which works for the mass mail merge emails). We are using a template we uploaded to CRM. I've confirmed they all have valid email addresses and all of them are set to allow for email and bulk emails in their contact forms. Then it reverted back to only sending an email to the 1st person in the list. That was great! So we used that same test marketing list and added about 40 more people. We found the mail merge worked when we created a test marketing list with only 3 people. We can verify the recipients exist if we do a preview in the word document template. We do specify ALL recipients when asked which recipients to send the mail merge too. We repeated this multiple times and it always sends to the 1st person (a different contact each time). We run it again, and it went to the 1st person again (which was the 2nd person from our first mass email attempt )since we excluded the successful one in this next attempt. As soon as we created a new marketing list with 50 people, it only sent to the 1st person. It worked in our 5 test email accounts when we sent those out (some were internal to our company and some external like gmail and hotmail). We have a mass mail merge email we are sending out.

Microsoft dynamics one doc merge