Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
Hello Everyone,
I'm trying to activate the Option Structure Show Parentage checkbox on the Gateway Export Wizard.
According to the Gateway User Guide the <show-parentage>true</show-parentage> is required in the appropriate <export-configs> of the gateway-tool-configuration.xml file, and that requires <filter-query-definition> to exist. Below is one of my attempts. The Gateway Wizard does not complaint about anything being wrong, but the option stays grayed out. Does anyone have any experince with this?
Thank you,
Francisco
.
.
.
<export-config>
<name>[SERVER] John Deere Template 1 MS Word Exporter -- with TOC page</name>
<description>John Deere Template 1 exporter that writes a Requirements Document document to Microsoft Word docx format -- with a Table of Contents</description>
<exporter id="MSWORD">
<property name="template">http://lsdewcs9.sdde.deere.com:7001/gateway/export/Microsoft Word/Deere Requirement Doc WordExportTemplate-2014a-TOC.docx</property>
</exporter>
<extension>docx</extension>
<title-field>Document Title</title-field>
<gateway-configuration-name>Deere Document Export</gateway-configuration-name>
<filter-query-definition>(not(field["State"]is empty))</filter-query-definition>
<show-parentage>true</show-parentage>
</export-config>
Solved! Go to Solution.
Hello Francisco,
Is this a client side configuration or a server side configuration?
Client:
Client mapping templates take precedence over server mapping templates. If you look in the config/gateway/mappings directory on your client, one of the files in that directory should have a mapping tag with an attribute value for name="Deere Document Export". In that same tag, what is the value of template-version?
If none of your client side mappings have that name, then the mapping is server side.
Server:
If you look in the data/gateway/mappings directory on your server, and you didn't find this on your client, one of your mappings should have a mapping tag with an attribute value for name="Deere Document Export". In that same tag, what is the value of template-version?
Regardless of whether you have a client or server mapping template, the template-version must have a value of 3.0 to work (at least, that's the template version that the <show-parentage> tag was added in--in the future, it will be allowed to have a higher value).
In general, you will get better performance with queries if you specify positive states rather than using a not operator. This is probably not an issue at the moment, but in the future, if the performance of this export seems excessively slow, you might want to change the not(field["State"] is empty) to specify particular State field values you are interested in (even if that is all State field values).
Aside to future readers: A valid <filter-query-definition> must also be set, as that is required by <show-parentage>.
I hope that helps.
Regards,
Kael
Hello Francisco,
Is this a client side configuration or a server side configuration?
Client:
Client mapping templates take precedence over server mapping templates. If you look in the config/gateway/mappings directory on your client, one of the files in that directory should have a mapping tag with an attribute value for name="Deere Document Export". In that same tag, what is the value of template-version?
If none of your client side mappings have that name, then the mapping is server side.
Server:
If you look in the data/gateway/mappings directory on your server, and you didn't find this on your client, one of your mappings should have a mapping tag with an attribute value for name="Deere Document Export". In that same tag, what is the value of template-version?
Regardless of whether you have a client or server mapping template, the template-version must have a value of 3.0 to work (at least, that's the template version that the <show-parentage> tag was added in--in the future, it will be allowed to have a higher value).
In general, you will get better performance with queries if you specify positive states rather than using a not operator. This is probably not an issue at the moment, but in the future, if the performance of this export seems excessively slow, you might want to change the not(field["State"] is empty) to specify particular State field values you are interested in (even if that is all State field values).
Aside to future readers: A valid <filter-query-definition> must also be set, as that is required by <show-parentage>.
I hope that helps.
Regards,
Kael
Thanks Kael, template-version was the issue. Once I updated that, the option came to live.