Missing Value Level metadata for QVAL in Dataset <dataset>

Hi Leonid,…

Hi Leonid,

Is it possible that you have an ItemDef element with OID "SUPPAE.QNAM"? If so, I guess that may cause the issue as OID should be unique within MetaDataVersion element.

Although there is no required naming convention for OIDs, the approach used in Define-XML 2.0 specification is a good one and can help to avoid issues. If it was used, the ItemDef OID for QVAL would be "IT.SUPPAE.QVAL" and ValueListDef OID for it would be "VL.SUPPAE.QVAL".

Provided sample code is not enough for diagnostics

Hi Leonid, 

Your sample code is not enough for diagnostics.

While defining Value Level Metadata you need to have 4 diffrent sections.

• QVAL variable has a reference to ValueList (3) -> (1)
• Each item in Value List has a reference to WhereClause (1) -> (2)
• Value Level item is defined by ItemDef element (4)

Here is an example:

(1)
<def:ValueListDef OID="VL.SUPPAE.QVAL">
    <ItemRef ItemOID="IT.SUPPAE.QVAL.SUPPAE.QNAM.AETRTEM" OrderNumber="1" Mandatory="No" MethodOID="MT.AETRTEM">
        <def:WhereClauseRef WhereClauseOID="WC.SUPPAE.QNAM.AETRTEM"/>
    </ItemRef>
    ....    
</def:ValueListDef>

.....

(2)              
<def:WhereClauseDef OID="WC.SUPPAE.QNAM.AETRTEM">
    <RangeCheck SoftHard="Soft" def:ItemOID="IT.SUPPAE.QNAM" Comparator="EQ">
        <CheckValue>AETRTEM</CheckValue>
    </RangeCheck>
</def:WhereClauseDef>

.....         

(3)         
<ItemDef OID="IT.SUPPAE.QVAL" Name="QVAL" DataType="text" Length="60" SASFieldName="QVAL">
    <Description> 
        <TranslatedText xml:lang="en">Data Value</TranslatedText>
    </Description>
    <def:ValueListRef ValueListOID="VL.SUPPAE.QVAL"/>
</ItemDef>

.....

(4)

<ItemDef OID="IT.SUPPAE.QVAL.SUPPAE.QNAM.AETRTEM" Name="SUPPAE.QNAM.AETRTEM" DataType="text" Length="1" SASFieldName="QVAL">
    <CodeListRef CodeListOID="CL.NY"/>
    <def:Origin Type="Derived"/>
</ItemDef>
....

Regards, 

Sergiy

Exceeding length

High risk of Truncated value SD1096 

Even when the variable is precisely 200 in length, this error persists. Could Pinnacle read supplementary variables in case truncation doesn't occur?

Exceeding length

Presumably "false positive" ...
I think that the algorithm (falsely) assumes that when the 200th byte is a non-blank, there should come more ...
And "High risk" is a stupid message ... How can such an algorithm even try to quantify a risk ...

Time to get rid of 40-year old SAS-XPT anyway ...