Go to the Plugins menu > Plugins Admin > find XML Tools in the list and click install. It’s free and it’s a great tool for various things. Here’s what you need to do: Download and install Notepad++ It turns out the tool I was using to check the file also has a plugin to validate a file against an XSD schema. So… this post may be useful to someone out there. The CRA website themselves said to check against a parser, but otherwise you’re completely on your own for where to find one and how to do it. The Finance team submitted the T5 XML file to the CRA for processing and a few hours later, we got a lovely email back, more or less scolding us for not checking the file against the XSD before submitting. What I ultimately missed was I had empty elements in the file, which I had assumed would be no issue as they are typically fine in other usages of XML in my experience. I made absolutely sure that I included every single element listed, validated the lengths and content types of the data, make sure I had no typos in my element names etc., I thought I was set. I had created all of the code, painstakingly checked the XML it created and ensured it matched exactly what the CRA’s specs had, or so I thought. So, if you’re an actual developer reading this, you’ll probably laugh, but I had no idea that was a thing. If you’re interested in the previous parts, part 1 is the story behind all of this, part 2 is a deep dive into the SQL code and syntax for the query, and part 3 is about getting the namespaces correct on the XML file. This would complete the list of things I learned in this journey to create a T5 XML file, that I didn’t know before I started. The last of the “technical” parts of this mini-series is about how to validate an XML file with a parser, against an XSD schema.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |