Convert Reader/ Writer to FeatureReader/ FeatureWriter

This is a good idea.

How about an 'import reader/writer settings from other reader/writer' on all (feature-) readers and

(feature-) writers?

I am glad someone suggested this! I was thinking, if we could right-click on a reader or writer and click an option to "Convert To Feature Reader/Writer" (and vice versa), that would be extremely helpful.

Please do this!

Yeah. Or something like a parameter "Act as a reader/writer" on the FeatureReader. When set to "Yes" the FeatureReader reads data without needing any triggers.

This would be great

This would be great

Failing the option of being able to convert from a standard writer, at least the option to Copy Feature Types from FeatureType as you can with a standard writer would be great.

When Safe starts implementing this very useful idea, I hope they implement at the same time my suggestion of one-click automatic database connection embedding, see https://knowledge.safe.com/idea/113615/enable-database-connection-embedding-for-transform.html .

I just added this idea exactly as a new idea (didn't find the idea before I posted mine): https://community.safe.com/s/idea/0874Q000000LP1CQAW/detail

For context, its quite a lot of work to replace a fully configured reader (someone else might have built) into a FeatureReader, my personal best practice is to always start with a Creator->FeatureReader to be more flexible, if the Creator is still there after 10 iterations, I might switch it to a Reader. Same with Writers vs FeatureWriters which currently support concurrent writing, rather than be limited by one writer active at a time and not be able to extend actions after writing in a new iteration of a workspace (luckily Writers will have the option of concurrent writing in upcoming versions).

Similar/exactly same idea as: https://community.safe.com/s/idea/0874Q000000TkbnQAC/detail

Please and thanks!

Genius ideea

Perhaps now is the time to look at migrating all functionality from the individual readers and writers into FeatureReaders/Writers and do away with the old order.

Merged Comments from Upgrad Reader / Writer to FeatureReader / FeatureWriter

• By hsamor on November 11, 2019 at 10:42 PM
  • Would be a real time saver!
• By bruceharold on September 9, 2019 at 9:02 AM
  • Duplicate of https://knowledge.safe.com/idea/33101/convert-reader-writer-to-featurereader-featurewrit.html ?
• By rileym on September 9, 2019 at 5:28 AM
  • I just came on to add this exact idea. Please, come on Safe, I have c.100 workspaces that have writers that I'd like to convert to FeatureWriters!
• By willcad on September 6, 2019 at 6:53 AM
  • Yes, please, by all means! I use FeatureReaders/Writers far more than standard Readers/Writers nowadays.
• By virtualcitymatt on January 25, 2019 at 4:53 AM
  • This would be super helpful!
• By revesz on April 27, 2018 at 5:54 AM
  • And convert back, too - until FR inputs/FW outputs are offered as inputs/outputs in FME Server. Moving featuretypes among FeatureWriters and Writers the same way as it works with Writers only would be also cool.

Merged Comments from: Replace Readers & Writers with FeatureReader/FeatureWriter Transformers

• By tjenarre  on April 25, 2018 at 8:25 AM
  • No love for this one? would be a useful feature.

Merged Comments from: Right click on Writer -> Replace with FeatureWriter

• By fmelizard on April 26, 2018 at 3:02 PM
  • Thank you very much for contributing your idea to the FME Knowledge Center, @tjenarre! We have identified that this request has already been captured in an existing idea – Upgrade Reader / Writer to FeatureReader / FeatureWriter– and this posting will be closed. We encourage you to upvote this idea (referenced above) and consider adding any comments to help define the criteria if you feel that it doesn’t cover all aspects of your request.

This would be very valuable. I’ve been thinking about this and needing it for some time, and only now came to the community to look for it.

Seeing as how it’s been around for 9 years and last updated 2 years ago, that’s not promising.

Aside from finding some more up-votes (178 as this time), is there anything else that would help to make this more viable or a higher priority, assuming it’s not currently in the product plan?

This would be a very useful addition - I came looking for this thinking Safe must have a solution for this but apparently not!