Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Also, I found that using File Geodb Arcobjects as 1st writer and Geodatabase SDE writer at second place, put inverse effect on writers. It writes the features as required (using filters and AttributeRenaming in FILEGDB but ignores for GEODATABASE_SDE.
ESRI Geodatabase (File Geodb ArcObjects) is a good choice, but it is not carrying forward all the attributes.Rather it carries only ObjectID, Shape, Shape.Area and Shape.len. Selecting Dynamic properties (giving schema source as reader), it writes all attributes as source, but ignores all other transformer settings (e.g., AttributeRenamer settings). Individually using FileGeodb ArcObject writer, works perfectly taking care of all filters and transformers. Using it as multi-writer, it loose a lot. I tried all settings, no success yet. Really there is something hidden.
Thanks Alex, this would help to move ahead. Using 'feature path' in FME and 'flatenning' I am able to transform, but resulting dataset gives different (FME generated) attributes, without geometry. So struggling to reach success.