Some time BI Publisher report got error due to special character in xml file.To handle this we have to modify xml file.
We have to use <?xml version="1.0" encoding="iso-8859-1"?> instead of <?xml version="1.0"?> it will allow report to run if data has some special characters.
If you are using rowset based xml generation use substitute function to replace the tag before writeline.
/* Create Sample XML File */
&strXMLFile = &ObjRowsetXSD.getXMLData(&rs1, &StrXMLfilepath | &StrXMLfileNm | ".XSD");
&strXMLFile = Substitute(&strXMLFile, "<?xml version=""1.0""?>", "<?xml version=""1.0"" encoding=""iso-8859-1""?>");
&SampleXMLFile.WriteLine(&strXMLFile);
If you are generating XML directly in code then use
&XMLdoc = CreateXmlDoc("<?xml version='1.0'
encoding=""iso-8859-1""?><ROOT/>");
Apr 15, 2016
PeopleSoft : Excel to CI Issue : User-defined type not defined
This issues comes mostly when using higher versions of windows operating system(Windows 8 and above) or using higher versions of Office (Above office 2007)
Follow the below steps to resolve the issue:
Solution 1:Need to enable macros
Step1: In excel to CI template
Press Alt+F11
Step2: Go to Tools->
References
Step3: Select “Microsoft AcitveX
Data Objects 6.1 Library” and “Microsoft DAO 3.6 Object Library” and
press OK button and Save the references.
Solution 2: Need to modify VB Script
Step1: In excel to CI template Press Alt+F11
Step2: In Menu bar go to Debug->Compile Excel to CI template, it will open the code with error
Step3: Replace "DOMDocument" with "DOMDocument60"
Replace "Set xHTTP = New XMLHTTP" with "Set xHTTP = CreateObject("MSXML2.SERVERXMLHTTP.6.0")"
Step4: Save the Document and compile again
Note:Some times Solution1 is not enough to resolve the issue Try both the solutions.
Subscribe to:
Posts (Atom)