Solved
InlineQuerier Issue
Has anyone noticed when Readers are replaced before an InlineQuerier that the it totally blows the InlineQuerier up? What is the best practice to stop this from happening?
Best answer by gio
Yes, you need to reset the IQ.
Afaikthats is the only thing you can do.
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.
Does that mean just totally re-do it? If that's the case Safe needs to come up with something better than that. A way to keep it connected when changing out Readers. That's pretty ineffective on Safe's part
+15- Contributor
Well not the only one of such.
Try making a complex customtransformer, export it as such.
Then ,like, use more than 1 instance in a workspace, and then decide to go editing it by changing/removing/adding parameters or attributes.....
But still..it is gettting better every new patch and release. :)