When we migrated to PB22, PBDOM_BUILDER.BuildFromFile worked fine

By the way, if you are using PB 2019 R3 or later you could do this replacement using .net.

Here is an example:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;
using System.IO;

namespace FixXMLClass
{
    public class FixXML
    {
        public static string loadAndFixXML(string xmlFile)
        {
            string xmlStr;
            
            if (!File.Exists(xmlFile))
            {
                return "";
            }
            
            StreamReader myReader = new StreamReader(xmlFile);
            
            xmlStr = myReader.ReadToEnd();
            myReader.Close();
            myReader.Dispose();
            
            xmlStr = fixXML(xmlStr);
            
            StreamWriter myWriter = new StreamWriter(xmlFile.ToLower().Replace(".xml", "_new.xml"), false);
            
            myWriter.Write(xmlStr);
            
            myWriter.Close();
            myWriter.Dispose();
            
            return xmlFile.ToLower().Replace(".xml", "_new.xml");
        }
        
        public static string fixXML(string xml2fix)
        {
            string fixedXML = "";
            
            fixedXML = xml2fix.Replace("&lt;", "<");
            fixedXML = fixedXML.Replace("&gt;", ">");
            fixedXML = fixedXML.Replace("&quot;", "\"");
            
            return fixedXML;
        }
    }
}

There are two methods (static).

• fixXML: Takes a string & replaces string causing the issue. It will returned fixed xml in a string.
• loadAndFixXML: Takes a file, reads its content, fix it using fixXML and finally creates a file like "<original_filename>_new.xml"

You could run those functions using .NET DLL Importer.

This will run very fast. After that buildfromfile will also run very fast.

Also, you don't really need to save the xml to the disk. You can directly build PBDOM using buildfromstring.

Andreas.

Hi.

You are not doing something wrong. The delay is because xml has &lt;, &gt; and &quot;...

If you replace:

• &lt; to <
• &gt; to >
• &quot; to "

you will find it will load super fast.

I guess PBDOM is trying to do that replace but I can't be sure. Such a replace in a big file can have big time cost.

Andreas.