> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/documentacion-editran-editran-sepa-v3-open-en/modo-de-uso/transformacion-con-warnings.md). # Transformation with warnings Given the asymmetry between the rules of the XML and flat-file formats in terms of the mandatory nature and content of the fields in each, sometimes the converter generates files that do not strictly comply with the rules of the final format (mandatory fields left empty, values different from those indicated by the rules, etc.) even though they do comply in the initial format. This result will be more common in XML-to-flat-file transformations because, given the temporary nature of the latter, priority has been given to meeting the requirements of the XML format. Thus, in that situation, as long as the initial file is correct, Editran/SEPA will generate the corresponding converted file but will end with a special Warning result (see the section [10.1 Receipt of the files](#101-recepción-de-los-ficheros)) in order to distinguish it from a file that does strictly follow the standard. By default, the scripts are defined to treat that result as correct, but it would be enough to modify them to define another type of behavior in that situation (move those files to another folder, delete them as is done with those that have errors, etc.). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.editran.onesait.com/documentacion-editran/documentacion-editran-editran-sepa-v3-open-en/modo-de-uso/transformacion-con-warnings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.