Define.xml

Description

Questions about creating and validating Define.xml

July 6, 2022

I'm trying to create the Excel Specification by first extracting metadata from SAS XPORT SDTM datasets. 

I am using the latest community version.  The part that I am talking about is the Define.xml tab > Create Spec. The configuration I am using is SDTM 3.3.

I put 30 datasets and only get Excel Specification with DM metadata, other datasets not in Excel Specification.

how does this happen? no error information about this situation and is there any requirements for XPT dataset and why P21 only recognize DM dataset?

Read More
July 5, 2022

Hi,

Please Clarify, DD0131 - rule expects that there is one to one match between Code list OID and Code list Name [Label] OR can we populate Common Code list Name for common variable [Example for Codelist OID=AE.DOMIN, DM.DOMAIN, CM.DOMAIN,... - can we have same Code list Name [Label] as "Domain Abbreviation" instead of "Domain Abbreviation (AE)" "Domain Abbreviation (DM)" "Domain Abbreviation (CM)",...? 

If we give same Code list Name [Label] for a set of Code list OID's then what could be the impact?

Read More
July 4, 2022

Hello,

 

Define xml v2.1 --> As per published sample define xml, Location Column is missing when HasNodata=Yes. But it seems, P21 validation expects the value. Attached screen shot for reference. Please provide your valuable suggestion.

Thanks.

Read More
June 22, 2022

Hi Team,

Please confirm how we can display the length for data types 'float'  and 'integer' at the variable level and value level.

 

data_type='Flaot' 

For example Variable AVAL :

one of the AVAL values has 12.3456789123, 

Varible level : Length = 8 . Siginificant_Digits = 10

Value Level : Length = 13 , Significant_Digits = 10 

data_type= Integer

For example Variable AVAL :

one of the AVAL value has 123456789123, 

Varible level : Length = 8.

Read More
June 21, 2022

Hi Team,

While creating define with version2.1 i am getting the following error "Invalid Standard Name value 'SDTM-IG'" and the value provided in define tab is 'SDTM-IG'. However as per rules it is stated 

 

Read More
June 21, 2022

Hi Team,

I am getting an error(Invalid use of Alias) for variable SEX while validating my define. Since I am using correct code list for 'M' and 'F'.

Could you please help me to resolve this issue?

 

Thanks,

Amit

 

 

 

 

Read More
June 20, 2022

Dear All,

 

As IE support was ended from Jun,2022, I try to view define.xml V2.0 through Edge or Chrome.

I converted the xml to html using SAS PROC XLS. But, I want the file format of the definition to be in xml format and I don't want to modify IT security policy either.

So, is there any solution to view define.xml in Edge or Chrome ? e.g. modifying Tag : <meta http-equiv="X-UA-Compatible" content="IE=edge"/>

 

Thank you for your help.

 

Best regards,

MinJi

Read More
June 13, 2022

Dear, Pinnacle 21 Staff

Even if I fill in Analysis Results Sheet with anything,
<def:WhereClauseRef> cord is not made at all in <arm:AnalysisDatasets> in Defien.xml.
Please instruct the entry example to the Excel Sheet.

Best regards, Sato

Read More
June 7, 2022

Thank you for pushing v2.1 functionality also into Community version. 

I had tried as suggested in your presentation to take CDISC's sample define.xml in the v2.1 release package and to create the P21 spec off it to see an example what needs to be filled in. 

Out of curiousity, I've loaded the P21 spec back into P21 to generated the define.xml again to see if it matches with CDISC's release but there are some differences: 

Read More
June 1, 2022

Where can we get the overview on newly added columns (i.e. Assigned Value, Common, Source etc...) in new template of SDTM/ADaM Specification generating from updated pinnacle 21 v4.0.1

Read More
Subscribe to Define.xml

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.