p Priyanka
on

 

Hi Team,

I am using Pinnacle 21 Community tool to generate the Define.xml , When I try to open the Define.xml file it opens with the Word and not in the webbrowser. Can you kindly guide on this .

 

Thanks,

Priyanka

Forums: Define.xml

l Lex
on August 25, 2016

Right-click and then Open With.

p Priyanka
on August 26, 2016

Hi Lex,

Thanks for your response. Can I open it from the Pinnacle 21 tool where the button says Open Define.xml? When I do so it opens in a word . Do I need to save the file at a location and then try to open with Internet explorer. I have tried to do so and save it along with define2-0-0 XLS style sheet file and tried to open it but still it does not open in the proper view. Do I need to have XML editor installed in my system?

 

Thanks ,

Priyanka 

l Lex
on August 26, 2016

When you right-click the XML file in the Explorer, you should be able to specify the application that you use to open the file with, and set that as the default. You do not need an XML editor.

p Priyanka
on April 2, 2019

Hi,

I am getting this error when the Value Level Metadata Origin is not matching the Variable origin. Since Value level can have multiple origins as for example LBORRES can have origin as CRF and eDT. Please confirm how should this error be dealt with while submission and mentioning in cSDRG . Also the origin for the Variable wit CRF page is mentioned with the Page number as in 3,4,5 while in Value Level it is getting split depending on the LBTESTCD. Please advise.

 

Thanks,

Priyanka

 

j Jozef
on April 2, 2019

If you have "Origin" defined on all you value-level definitions for a specific variable and one of them differs from the one at the variable level, then do NOT define the Origin on the variable itself. If your define.xml is generated by a "black box" tool, you can still use an XML editor or simply NotePad++ to remove the one at the variable.

Jozef Aerts - CDISC Define.xml trainer

p Priyanka
on April 4, 2019

Hi,

I tried doing so. I have made the Origin as Blank for Variable level for LBTESTCD. In this case it throws an error for DD0072 Missing Origin.

 Please advise.

j Jozef
on April 4, 2019

At the variable level, you should then leave def:Origin completely out - not blank, so NOT:
<ItemDef OID="IT.LBTESTCD" Name="LBTESTCD" ... ><def:Origin /></ItemDef>
NOR:
<ItemDef OID="IT.LBTESTCD" Name="LBTESTCD" ... ><def:Origin Type="" /></ItemDef>
but instead
<ItemDef OID="IT.LBTESTCD" Name="LBTESTCD" ...>...</ItemDef>

If you then still get the "Missing Origin" error, then it is a false positive error.

From the define.xml specification: "For regulatory submissions, def:Origin metadata must be provided for all SDTM, ADaM or SEND variables. It is at the sponsor's discretion whether to provide def:Origin at the Variable or Value level."

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.