Forums: Troubleshooting and Problems
I think I can answer my own questions ... :-),
as it is all in the document at https://www.pharmasug.org/proceedings/2018/DS/PharmaSUG-2018-DS20.pdf and just trying a few things out also helped ...
XML output seems not to be supported. Although the console says something about taking "xslx" as "the default".
For the input, it looks as Dataset-XML files are automatically recognized, and there is no need to provide a parameter for it. I tried it out and it works perfectly.
I haven't tried it out for CSV yet.
Hope this also helps other implementing the CLI - I already managed to do it for starting CLI validation from within our popular SDTM-ETL mapping software for which we are currently developing v.4.0 and that will also work with the new "CDISC Library API".
With best regards,
Jozef Aerts
XML4Pharma
Some more questions regarding CLI that came up during installations at customers ...
a) in the past it was possible to obtain the report as XML. Is this still so?
If yes, what is the command line parameter to indicate XML output report is requested?
Some of my customers have processes where they transform the XML to PDF for internal team discussions and for archival.
b) what is the command line parameter to indicate that the input files are in the modern CDISC-Dataset-XML format?
Many thanks in advance!
Jozef Aerts
XML4Pharma