Currently looping with blocking transformers is only allowed in linked custom transformers. (see http://knowledge.safe.com/articles/1273/looping-with-blocking-transformers.html)
However there are transformers that force a linked rather than embedded custom transformer are only blocking if they have a Group By, or other parameter setting that causes them to block.
It would be nice if these transformers could be used in an embedded loop when they are not in "blocking-mode"
ex. Bufferer (No Group By), AreaAmalgamtor (Self-Amalgamation Mode), PythonCaller (Function)
Archived
Allow embedded loops with potentially blocking transformers
+40- Contributor
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+40- Influencer
It would be nicer, if the concept of forcing embedded transformers to be linked was abandoned altogether.
I think it might be implemented by having FME automagically create a hidden temp linked transformer on-the-fly from the embedded template whenever needed in the translation.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.