The export can be performed per task with the FeatureQueryFilter to restrict the export to certain objects. Attention should be paid to the fact that the spelling of the queries is directly dependent on the used data source. It is therefore a good idea to test these in the GIS in the definition query of the feature class and then copy them to the configuration.

 

 

 

Example: Only the objects whose attribute Layer has the value GP, are exported.

 

Spelling of the Where Clause:

The type or notation of the Where Clause depends on the underlying database. The Where Clause for a Filebased Geodatabase looks different than for a Personal Geodatabase. e.g. fGDB > ' pGDB > "

The correct notation can be found out via the query builder in ArcMap.

 

The operators LIKE and IS UNLIKE (<>) must be written in the configuration as follows

 

•LIKE:
<FeatureQueryFilter Where="KGNAME LIKE'%en%'" />

•<>
<FeatureQueryFilter Where="Layer&lt;&gt;'VS'" />
The "is not equal"; query must only be entered in this form when using Notepad++ or other text editors; designated XML editors (e.g. XML Notepad 2007) perform UTF-8 encoding automatically when saving, i.e. the entry must be made there as <>
 

 
The input lt;> becomes <FeatureQueryFilter Where="Layer<>'VS'" /> in the XML and returns an "Underlying DBMS error" during CAD export "Underlying DBMS error" with the error message "A non-boolean expression was specified near ';' in a context where a condition is expected"