[Name] FEATURE_TYPES [Description] Allows the user to pick from the various feature types of a format. Returns these as an FMEStringArray. The connection information necessary to create the FMEObjects connection will be specified in , which can contain macro references. If it contains macro references, then those macros must have values before the feature type picker can be enabled. Macro references can be specified as $[]. There is one exception: when specifying the value for _DATASET_OVERRIDE_ as macro reference, do not enclose the macro name in square brackets. Instead just specify the macro name as the value for the directive. E.g _DATASET_OVERRIDE_ SourceDataset_MDB_ADO_1. The connection string should contain the location of the dataset, followed by key-value pairs. For example: $[DATASET],SERVER_TYPE,$[SERVER_TYPE],USER_NAME,$[USER_NAME],PASSWORD,$[PASSWORD] Optionally dataset and format override can be provided like this: $[DATASET],_DATASET_OVERRIDE_,,_FORMAT_OVERRIDE_,,SERVER_TYPE,$[SERVER_TYPE],USER_NAME,$[USER_NAME],PASSWORD,$[PASSWORD] Optional directives or keywords that are processed include: - REMOVE_SCHEMA_QUALIFIER - LIST_WORKSPACES - _FORMAT_OVERRIDE_ - If specified then its value will be used for the format name. - _DATASET_OVERRIDE_ - If specified then its value will be used instead of the $[DATASET]. Value for this directive is the macro name to use for source dataset. Do not enclose the macro name in square brackets (like $[...]) - _DEFAULT_FILTER_ - Provides a default filter for the feature type list. We might also have a syntax (like -$(MACRONAME)) to indicate that a blank value for that macro is okay (i.e. for Oracle dataset, or ODBC password). Note that RETRIEVE_ALL_TABLE_NAMES YES is automatically added to the connection string for FEATURE_TYPES. To have FEATURE_TYPES GUI directive work, you need to use two special macro names. Macro DATASET is used to pass the value of dataset between source/destination prompt and setting box. Macro TABLELIST is used by the GUI framework to temporarily store the feature type list and then convert to ID list for the reader. See example below. Similarly the macro DESTINATION_TABLELIST is used for the special cases where the writer uses the reader::readSchema() call to populate its schemas. In a Transformer (*.fmx) File Syntax PARAMETER_NAME: PARAMETER_TYPE: FEATURE_TYPES PARAMETER_PROMPT: