Enhancements and Feature Requests


For submitting enhancements and feature requests and new project ideas.

March 8, 2021

Dear P21,

When validating ADAM data package in P21E, we could specify the MEDDRA version. But in P21C, there is no place to specify MEDDRA version when validating ADAM data packages. Is there any reason why there is such different setting? Thank you very much. 

Read More
March 7, 2021
  1. Use P21E to validate the define.xml version2. Currently, our company created a Linux utility m-mkxml2  to create and upload the define.xml version2 to P21E for validation. I tried to put only the define.xml and define2-0-0.xsl in the .zip package and upload to P21E for validation. And there seems no report created for define.xml. So just wonder how other companies get the P21E define.xml v2 validation report if they did not use the Linux m-mkxml2 -e utility. Is there other way to get the P21E define.xml v2 validation report other than using the Linux utility?
Read More
March 7, 2021

For Pinnacle 21 community, we could only validate the SAS .xpt datasets and the define.xml. In the future, will Pinnacle 21 community add functionality to include data reviewer's guide, XLS stylesheet, SAP, tables (as reference files for define.xml ARM) in the validation package?

Read More
March 6, 2021

P21E study data packages, once it is created, we could not delete it but can only deactivate it. Is it possible that P21E provides us the functionality that we could delete studies or data packages that are no longer used? Or are there any reasons we could not delete them? For example, for cost traceability concern? Thank you. 

Read More
October 15, 2019

Only "Configuration:", "Define.xml:", "Generated:", "CDISC SEND CT Version:" and "Validation Engine Version:" are printed on the sheet "Validation Summary" of Pinnacle21 Validator Report.
In this content, we do not know when the report was executed with which version of the validator, so please add the printed version of the executed validator.
best regards

Read More
September 2, 2019

Dear all,

In the blog "Introducing P21 Community 3.0" of May 8, 2019 it was mentioned that "an updated and more detailed CLI documentation will be published in the near future" (see attached screenshot).

When will this become available? The current documentation (P21 website + PharmaSUG paper) is quite limited and does not discuss all available CLI parameters.

Thanks for any update,
Jeroen Den Herder (SGS Life Sciences)

Read More
May 14, 2019


I can't execute the new pinnacle 21 because I have a windows 32 bits.

Woult it be possible to have a download for Windows 32 bits.




Read More
May 12, 2019

Hi Pinnacle 21 team,

Many programmers in our industry have problems with installation of external software in their working environment. Previously it was not an issue, because nothing was installed. I know it is not your problem, but having a portable version will solve this issue.

I may be wrong, but as I understand you are using Electron now. Electron-builder has a portable target for windows, which should make it easy to generate such package.

Thank you.

Read More
May 10, 2019


I would like to know if, in future version, you could let the user select the location of the Pinnacle 21 Community 3.0.0 folder containing the configs/defines/logs/reports. Our IT department do not allow us to store files in "My Documents" and they prefer that we use our personal server.



Read More
April 12, 2019

The PhUSE Optimizing the Use of Data Standards Working Group ("Define-XML 2.0 Stylesheet Recommendations") released a new Define-XML 2.0 Stylesheet in November 2018.
This stylesheet is a big improvement over the previous Define-XML v2 stylesheets as published by CDISC.

See: https://wiki.cdisc.org/display/PUB/Stylesheet+Library

Read More
Subscribe to Enhancements and Feature Requests

Want a demo?

Let’s Talk.

We're eager to share and ready to listen.

Cookie Policy

Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.