CLI validator output not showing all issues

Same Issue

I just posted another thread--we seem to be having the same issue.  We're using the SDTM 3.1.3 (FDA).xml configuration.

Config does not use CLI validator property.

It looks like 2.0 CLI does not load Controlled Terminology codelists, it can be noted by a log review, which will be full with messages like:

The ItemDef IT.AE.AEACN contains a reference to the unknown codelist CL.C66767.ACN

The issue is that when someone is passing condif:cdisc parameter to CLI 2.0. it sets "CDISC.Version" property at line 304 of the CommandParser class. While in every CDISC configuration file, a reference to the folder with Controlled Terminology contains "CDISC CT.Version" property.

You can try doing either of the following:

1) Update all configuration files by changing %System.CDISC CT.Version% to %System.CDISC.Version% (tested)

 2) Update the CLI code to set CDISC CT.Version instead CDISC.Version. (not tested)

Interactive v. Command Line

Dmitry--thanks!  Two quick questions...

(1) Will changing the configuration files cause problems for the interactive front end when it tries to find the CT lists?  That is, does the interactive front end look for %System.CDISC CT.Version% and will it fail if all it finds is %System.CDISC.Version% ?

(2) The CLI code we're currently using is, e.g.,

-config:cdisc="2014-09-26"

I'm assuming the ".Version" is automatically appended, but can we just say -config:cdisc ct="(date)" or will the space cause a problem?  Does a two-word value need to be escaped or quoted somehow?

Dave, yes, it will cause

Dave, yes, it will cause problems, GUI version does not work for me with the updated configuration.

In the second solution I was refering to the source code update. I'm afraid you cannot specify a property name in a command line.