Troubleshooting and Problems

There is a small error in the CLI description at https://www.pinnacle21.com/projects/validator/community-cli
The command parameter "--source.defne=" must be "--source.define="
with "--source.defne" the CLI start will crash

Hi,

Please let us know the following connection destination information required to connect pinnacle21 community version 3.0.0 to the Internet under a firewall environment:

1) IP address
2) Communication protocol
3) Port number

Thank you for your continued support.

Dear, Pinnacle 21 Staff

The first sheet "Validation Summary" of SDTM/ADaM/Define P21C 3.0 Validator Report files is protected by unkown password.
We want to unlock the sheet's protection each time, for the purpose of hiding the configuration folder path entered personal username.
Could you tell us the password?

Best regards, Sato

Dear, Pinnacle 21 Staff

It appears that in the new version of Pinnacle Community, when define.xml is generated from an Excel spec document, the ItemDef OIDs for value-level metadata are based upon the WhereClause. For instance, our metadata for ADPP.AVAL depends upon the value of ADPP.PARAMCD, resulting in ItemDefs like

Hi,

I have noticed with version 3.0.0 we now get "validator installation messages" which are very useful but also tad confusing.

For example, when I downloaded version 3.0.0 of P21 Community it came without the latest SDTM and ADaM terminology documents, version 2019-03-29. So after updating the dictionaries (as per the instructions on the P21 forum) I got these "validator installation messages":

Hi,

I ran CLI validator 2.2.0 on SDTM data using SAS. However the report generated has software version as 2.1.2 and not 2.2.0.  Also i have noticed the validation report using CLI vs GUI is different.  There are also differences in warnings and errors for 2 domains FA and TS.  Attached is a document with differences. Please advise. Thanks a lot for your help.

NA.

Hi,

I tried to run P21 3.0 CLI under Windows 10 64bit, following Validation CLI, but failed.

Below is the command

  java -jar p21-client-1.0.0.jar --engine.version="FDA 1903.1" --standard=sdtm --standard.version=3.2 --source.sdtm="." --cdisc.ct.sdtm.version=2018-12-21 --ndf-rt.version=2018-02-05 --report=".\report.xlsx"

And below is one of the messages from the log

Hi all,

In Community version 2.2.0 I was able to easily add custom configurations of the standard define.xml which we used to conduct early and mid-study validations for which not all of the validation rules would necessarily apply. Adding these additional files int he \compnents\config folder wold cause them to appear in the desktop application. I have yet to figure this out for the 3.0.0 version. Any hints would be appreciated.

Cheers.

Hi,

I used to run the p21  in SAS by calling components\lib\validator-cli-2.1.5.jar using x command for version 2.2.  I was wondering if we do have the same for version 3.0 if we do, in which folder we will get this information. Many thanks for your help.