VERSION(S): E-Collaboration 2.1 SITUATION IDENTIFIED IN: E-Collaboration 2.1 document export. SITUATION DESCRIPTION: Documents exported by E-Collaboration 2.1 are XML files. This means that certain characters ( & ' " < > ) are encoded. For example the character & will be sent as & . Sometimes this is not desirable e.g. when the exported files are sent to a Baan system as an EDI message. SOLUTION DESCRIPTION: The coding of characters in the E-Collaboration output can be disabled by making 2 changes to the "Mapping XSL File" as specified in the "Send method". Use a new name space (xmlns:xsl="http://www.w3.org/1999/XSL/Transform") to indicate the use of XSLT instead of normal XSL. Disable character coding (in XSL terms disable output escaping). This can be done in two ways: First use the attribute disable-output-escaping="yes" inside the xsl:value-of or xsl:text methods. Or alternatively set output to text by adding the following tag 'xsl:output' just after the starting tag 'xsl:stylesheet'. The beginning of a XSL file that makes use of XSLT to disable character encoding looks e.g. like this: Whereas the beginning of a XSL file which does not make use of XSLT looks like this: To make use of XSLT an upgrade from MSXML2 (the parser supplied with E-Collaboration2.1) to MSXML3 is necessary because MSXML2 does not fully support XSLT. The following steps are required to install MSXML3 on the Webserver: 1 Put all the files of this solution in a Temp directory on the local harddisk. 2 Close all applications, which work with the MSXML. When the installation does not start because MSInstaller is not installed first Run InstMsi.exe. 3 Run msxml3.0.exe and use all the defaults. 4 Run the xmlinst.exe After this a reboot of the Webserver is required. The solution can be found on the Support FTP Site. It contains 3 files. 1 - readme.txt: This solution description 2 - msxml3.exe 3 - xmlinst.exe 4 - InstMsi.exe ftp://ftp.support.baan.com/updates/E-Enterprise/E-Collaboration/2.1/Solutions/2.1.0.120292.