Parsing XML/Invalid Document Structure at Line 1 Column 1 (again)

[jdemeyer]

Greetings!

I'm attempting to parse an XML file.  When I point the Input Data tool at XMLFile2, the tool indicates "Invalid Document Structure at Line 1 Column 1".  When I point the Input Data tool at XMLFile1 or XMLFile3, the tool indicates no errors.  All the files are located on a network drive. 

I have successfully opened, parsed, and processed data from all three files (without errors) in Python on my local machine.  Also, I review the files in XML Spy and UltraEdit to help look for subtle differences and found nothing obvious.

I have also attempted to change the name of the GalleryAlias file without success (this was suggested in similar posts on this forum).

I moved the file to a local location (not a network drive) without success.

Other thoughts on this error?

Thanks!

Joe

[apathetichell]

Do you have "ignore errors and continue" checked?

[jdemeyer]

Thanks for replying!

When I check "Ignore errors and continue", the error message changes to "No Root Element".

Joe

[apathetichell]

Are you clicked on "root" - do you get the same error on "auto-detect child"?

[jdemeyer]

Thanks for the suggestion!

On XMLFile2

Return Root Element clicked: "No valid XML to Parse"

Return Root Element and Return Child Values clicked: "No valid XML to Parse"

On XMLFile1 and XMLFile3, no errors.

All XML files have the same schema.  They contain different data by date.

Joe

[danilang]

hi @jdemeyer 

Can you post the first few lines of the broken xml?

Dan

[jdemeyer]

Thanks for asking!

I opened the file in Notepad and pasted it here.

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="TransactionReport.xsl"?>
<XMLOutputEntity xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<InsuranceFileUploadLogID>999999</InsuranceFileUploadLogID>
<InsuranceSubmissionCompanyCode>99999</InsuranceSubmissionCompanyCode>
<UploadedFileName>XMLFile2.XML</UploadedFileName>
<Comments />
<CompaniesTransactions>
<XMLOutputCompaniesTransactionsEntity>

I changed the data in the InsuranceFileUploadLogID and InsuranceSubmissionCompanyCode nodes; it is representational.

Joe

[hellyars]

@jdemeyer 

I am not sure if this pertains to your issue, but just in case...

There is a known issue with the XML parse tool and the detection of specific child elements that appeared with the release of 2020.4.  Here.  The temporary fix did not work for my XML source documents.  Hopefully the next patch resolves the issue.  

[jdemeyer]

Thanks!

I suspect the issue may apply.  I use Alteryx Server 2020.1.

Any updates on the efficacy of a 2021.x patch on this issue?

Joe

[danilang]

hi @jdemeyer 

Do the other 2 files have the highlighted line

Dan