Troubleshooting and Problems

Description

When things just don't seem to work

August 23, 2016

We're working on producing a define.xml from from a spec spreadsheet in Excel, using the Pinnacle21 system. We're noticing that for value-level variables, the where clause will be duplicated if the same text is used to qualify two or more variables. In the attached example, DRVMTH and one other variable are both qualified by PARAMCD, which is normal, but the where-clause gets repeated. It is worth noting that we have checked that the WhereClause ID is definitely distinct.

Read More
August 18, 2016

I've verified this using a few versions of OpenCDISC and Pinncle21 versions.

Read More
August 12, 2016

The newest version appears to be using USUBJID, SUB:SITEID rather than USUBJID, SUBJID when cross checking within a SEND dataset.  This is resulting in ERRORS in every domain except trial design and DM.  This bug was not present in 2.1.1.

Read More
August 10, 2016

Hi,

I'm validating with the latest version (2.1.2) and get the warning "Missing FWENDY variable, when FWENDTC variable is present" for my FW dataset.  While I don't have the FWENDY column and do have the FWENDTC column, I don't have the FWDY column in the dataset.  I think without the FWDY present, having the FWENDY wouldn't make sense and this rule should not report.

Thanks!

Read More
August 10, 2016

Hi,

I'm using POOLID instead of USUBJID for all of FW and a handful of records in LB in a SEND submission.  When I ran the latest validator (2.1.2) on the submission, it's identifying all those records as duplicate records.  In the Variables column of the report it shows that it's evaluating it based on the USUBJID column (all NULL values) and not the POOLID column.

I know I can ignore this, but it's probably something that shouldn't be warned about if the POOLID is present and populated.

Thanks!

Read More
August 2, 2016

Trying to invoke the CLI validator in Pinnacle 21 Community v2.1.2, and I'm getting the same sort of errors I was getting previously:

Read More
July 25, 2016

In previous versions of OpenCDISC, unprocessed datasets were in a separate section on the Dataset Summary Tab.  Now they seem to be included in the Processed Sources tab with the Class of SYSTEM. This gives the wrong impression to users that the dataset was checked and has no errors or warnings. On the second tab Issue Summary you list them as Dataset xxxx not validated. Can you please fix this display on Dataset Summary Tab to be included in the 'Unprocessed Sources' section?

Read More
July 18, 2016

Hi,

For EG.xpt file was ran through the validator tool. A warning appears that indicating "EGLEAD variable is in wrong order with in domain "  but i have conformed the order of the variables matches the SEND IG 3.0

Currently we are using  Open CDISC Community 2.1.0 and we have tried  the latest version of 2.1.1 but we are facing same warning.

 

VARIABLE, DATASET
EXMETHOD, EX
SD1079
FDAN035
Variable is in wrong order within domain
MetadataWarning

 

Please reple as much as possible.

 

Thanks,

Read More
June 30, 2016

Hi There,

I am new here so I hope this is not a silly question.

I have created a define.xml (v2.0) in Pinnacle 21 and for some reason it does not show the stylesheet format, the styleesheet is saved in the right folder and it works with other .xml files in the same folder... Am I missing something?? When I view the xml file I created in Pinnacle 21 it just looks like black text on a white background.

Any help would be much appreciated!!

Thank you!

Read More
June 29, 2016

I am new to Pinnacle 21 (nee OpenCDISC).  The company has the latest Java version, v8, running.  I tried using 'VALIDATE' for an ADAE.xpt file and it hung.  Any suggestions?  Is it the version of Java that we are using?  TIA.

Read More
Subscribe to Troubleshooting and Problems

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.