Hi @avineon, "fme_feature_type" stores the source feature type name and FME will treat it as a Schema Definition Name (identifier of the schema configuration in the source feature type). You therefore should not modify the value of "fme_feature_type", if you intend to configure the destination schema according to the source schema dynamically.
If your requirements were:
- write the features into a destination feature class named "dataset_fuse",
- apply the schema derived from the source feature type to the "dataset_fuse" class,
try configuring the dynamic writer feature type as below. Here, assuming that the source dataset contains only a single feature type. Do not change the value of "fme_feature_type" which is retrieved from the source dataset.
Hi @avineon, "fme_feature_type" stores the source feature type name and FME will treat it as a Schema Definition Name (identifier of the schema configuration in the source feature type). You therefore should not modify the value of "fme_feature_type", if you intend to configure the destination schema according to the source schema dynamically.
If your requirements were:
- write the features into a destination feature class named "dataset_fuse",
- apply the schema derived from the source feature type to the "dataset_fuse" class,
try configuring the dynamic writer feature type as below. Here, assuming that the source dataset contains only a single feature type. Do not change the value of "fme_feature_type" which is retrieved from the source dataset.
If you want to create a new "Feature Dataset" named "dataset", set another parameter in the writer feature type, like this.
Note: You have to use GEODATABASE_FILE writer to create a new feature dataset. The FILEGDB (File Geodb Open API) writer doesn't seem to support creating feature dataset.
