XML input errors
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
After changing to Version 2022.3.1.615 Patch 10, a workflow with XML as the input data is no longer working correctly. It is skipping files and has this error message: Warning: Input Data (3): The file "tblDistricts.xml" has a different schema than the 1st file in the set and will be skipped.
Have there been changes to handling XML files? The first file works and then I get the error on the second file.
Sample files are attached.
Solved! Go to Solution.
- Labels:
- Input
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
@PeggyWitt can you please provide more data.
How do you import the files into Alteryx? Very hard to tell from just reading your post, more details are needed.
I did not get any error when trying to import these 2 files into Alteryx in several different ways and from opening the files and reviewing the XML both has the same schema.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi OTrieger,
Thanks for replying to my post. I’m just using the standard input tool and selecting XML for the type of file. I agree that they are the same schema.
Being it works for you, could you please tell me what version you are using?
The workflow worked for years but now after I updated to a newer version I’m getting the errors. I even tried previous successfully processed data and got the same errors. I am hoping a different version will take care of the problem.
Thank you, Peggy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Version: 2023.1.1.392 Patch: 7
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi OTrieger,
Well, that didn't work. I upgraded to the newest version, 2024.1.1.136. I am still getting the same error message and it is skipping many files.
I looked at the XML Parse tool example, but the example starts with an Alteryx database. I am using the standard Input tool with the selected File Format Extensible Markup Language (.xml), so the example is no help.
My 57 .xml files are in separate folders, so I also have checked "Search SubDirs". I have included more files below in hopes that the error will come up for you.
Is there any other way to input and parse .xml files?
Thanks, Peggy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hello @PeggyWitt,
It is possible to alternatively read in XML files as CSV format, you can then process the files using the XML Parse tool. Attached is a sample workflow that is able to read in the 5 sample attachment files properly, I also enabled Search SubDirs. Provided all the files has the same column structure, they should be able to be read in without any problems.
The Input Tool is configured to read in the XML files at the parent directory and all subdirectories (.\*.xml with Search Subdirs enabled), therefore I would recommend that you place this workflow into the parent directory containing the XML files. However, if you wish to place the workflow in a directory which is not the parent directory containing the XML files and change the address configured in the Input Tool (for example as C:\Users\SampleUser\XML_Project\*.xml), the input tool will automatically configure itself from CSV mode to XML mode again, at which point you will have to reconfigure the tool for the workflow to function properly. For this reason, I am also attaching a screenshot which contains the proper configuration for the Input Tool.
Could you also please tell me which version of Alteryx Designer you upgraded from (before using 2022.3.1.615 and 2024.1.1.136)? Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
hypothesis the error is because a field contains/or does not contain a subset of data which is allowing it to be populated incorrectly as the wrong datatype (boolean or number). this is creating an issue when a dataset with a non-conforming datatype is in that field. I'd recommend brining in all the files via batch macro - vs dynamic input/input data with wildcard and seeing how it looks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi NeoInfiniTech!
You are a life saver! Your solution worked beautifully. Also very easy to understand and implement. Thank you so much for your help.
Previous version was 2020.4.5.12471
Peggy
