Hi,
there is unfortunately no easy and foolproof way of doing this, except by using the WorkspaceRunner.
It is possible to hack something together using the SQLExecutor and/or the FeatureHolder, but you risk that it will be ugly and difficult to maintain.
There has been prior discussions on this forum regarding this functionality, and one suggestion that surfaced was that the writers should also have an optional output port, so that it was possible to chain them (a bit like the Logger in FME2013).
I'm not sure if this feature request has been logged with Safe already, but it could be a good idea for you to pass this on to them regardless. The more people who request this functionality, the more likely it is to be implemented in the future.
David
Hi Imran,
I agree with David.
One more consideration, can you adopt the workflow like this?
Takashi
Hi,
there is unfortunately no easy and foolproof way of doing this, except by using the WorkspaceRunner.
It is possible to hack something together using the SQLExecutor and/or the FeatureHolder, but you risk that it will be ugly and difficult to maintain.
There has been prior discussions on this forum regarding this functionality, and one suggestion that surfaced was that the writers should also have an optional output port, so that it was possible to chain them (a bit like the Logger in FME2013).
I'm not sure if this feature request has been logged with Safe already, but it could be a good idea for you to pass this on to them regardless. The more people who request this functionality, the more likely it is to be implemented in the future.
David
I like the reader output port option!!! I did try and use the SQLExecutor and/or the FeatureHolder pattern for my problem but it did not appear to write the features before the SQLExecutor...
I like the reader output port option!!! I did try and use the SQLExecutor and/or the FeatureHolder pattern for my problem but it did not appear to write the features before the SQLExecutor...
@fallingdog Since FME 2016 there has been a FeatureWriter transformer which does exactly what @david_r suggested. See FME 2016 Sneak Peek: The FeatureWriter Transformer and https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Transformers/Transformers/featurewriter.htm
@danatsafe is there a way to get the feature writer to return the feature and an ID (key) that is populated by the target database when the feature is written to an output port? right now I am using a feature reader after the feature writer....
@danatsafe is there a way to get the feature writer to return the feature and an ID (key) that is populated by the target database when the feature is written to an output port? right now I am using a feature reader after the feature writer....
In this case you will need a FeatureReader after the FeatureWriter to get those keys.
In this case you will need a FeatureReader after the FeatureWriter to get those keys.
Great sounds like I am doing it right! Thanks @danatsafe!
