When things just don't seem to work
Following updates on 07-April-2021, there is no longer an option for a non-legacy FDA engine that can be used. Is there an updated engine that is missing as the previous FDA 1907.2 now indicates 'Legacy' and results in errors within the validation reports.
Hi,
UNII versions 2020-10-19 and 2020-11-16 are unavailable in P21 Community Version: 3.1.0.
Thank you for your support.
Regards,
Hello,
I have developed a CLI tool to validate SDTM and ADaM datasets from SAS. The tool works about 50% of the time, but often fails with warnings output to the java log. However, the command / java code is identical with each case. What could be causing this fail sometimes with "Failed to process encrypted file" and "Failed to process eTag file" warnings?
NOTE: internal paths below were replaced with "<path>"
Goodmorning,
Thank you again for your precious work.
I m trying to validate tmy define for SEND using PINNACLE CLI fllowing instructions present in PharmaSUG-2018-DS20.pdf for SDTM(Example 6).
This is my code:
java -jar p21-client-1.0.3.jar --standard=send --standard.version=3.1 --source.define="******\define.xml" --cdisc.ct.send.version=2020-09-25 --report="******\define-report.xlsx"
I get this eerror:
Goodmorning,
Thank you for your precious work.
I m trying to create the define template for SEND using PINNACLE CLI fllowing instructions present in PharmaSUG-2018-DS20.pdf for SDTM(Example 4).
This is my code:
java -jar p21-client-1.0.3.jar --standard=send --standard.version=3.1 --source.send="******\xpt\" --output.format=define-excel --output="*******\define_original.xlsx" --cdisc.ct.send.version=2020-09-25
I get this eerror:
Since this weekend a few of us are getting the following error: 'No internet connection - Reconnect to get the latest updates, configs, and notifications.' We are all on the latest version. We can still run the validation but the issue is some of us are getting additional warnings on our report output that 'Problems with your Validator installation detected which may cause inaccurate validation results' while others are not. Obviously it's not an internet connection issue, so wondering if others are seeing this or know what's going on?
In P21E, For CT2002: RSSTRESC value not found in 'Tumor Response Result" extensible codelist.
For which code list is this referencing?
Hello,
We've encountered an issue where we are not seeing flags for Nonstandard Terminology when validating our SEND datasets against the newest 2020-12-18 CT. We've confirmed they are still showing up when validating against older versions.
Thanks.