Glad to hear that it works Dan,
cant see anything obviously strange, we will look into this and see if
we can fix the inconsistency.
Best,
Syed
Dan Staines wrote:
OK, I've now tested the earlier idea that the redundant
SpecificOptionContent.tableConstraint field in the template was throwing
things off, and it seems that this is the correct thing to do, as my
filter now works properly. Weirdly, the final value of tableConstraint
in the option hasn't changed!
Template is now:
<Option checkForNulls="true" displayName="EntrezGene ID(s)"
displayType="text" field="dbprimary_acc_1074" internalName="entrezgene"
isSelectable="true" key="gene_id_1020_key" legal_qualifiers="=,in"
multipleValues="1" qualifier="=" tableConstraint="ox_EntrezGene__dm"
type="text">
...
<SpecificOptionContent field="dbprimary_acc_1074"
internalName="dmelanogaster_eg_gene" key="translation_id_1068_key"/>
which gives the final config after export:
<Option checkForNulls="true" displayName="EntrezGene ID(s)"
displayType="text" field="dbprimary_acc_1074" internalName="entrezgene"
isSelectable="true" key="translation_id_1068_key"
legal_qualifiers="=,in" multipleValues="1" qualifier="="
tableConstraint="ox_EntrezGene__dm" type="text"/>
(which MartEditor also says: "ox_EntrezGene__dm")
compared to the non-working:
<Option checkForNulls="true" displayName="EntrezGene ID(s)"
displayType="text" field="dbprimary_acc_1074" internalName="entrezgene"
isSelectable="true" key="translation_id_1068_key"
legal_qualifiers="=,in" multipleValues="1" qualifier="="
tableConstraint="ox_EntrezGene__dm" type="text"/>
So, whilst I'm delighted this is working now, would anyone like to
hazard a guess at what has actually changed and why I get this behaviour?
Cheers,
Dan.
