SQL Creator is working fine while parameters are provided in query itself. But its not working while using published parameters and embed connection parameters.
Question
SQL Creator not working with Published parameters
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.
+26- Contributor
I tested this in FME 2019.0 and can confirm the issue.
Seems that the published parameter in the SQL statement is not replaced by the value given for the published parameter.
Please submit this to www.safe.com/support as it seems a bug.
+16- Contributor
Published Parameters can sometimes not work as intended when used within a workspace and I find that it's good practice to first use a ParameterFetcher to put the parameter values into attributes.
In your case, as you're using a SQLCreator, you may need to replace that with a Creator > ParameterFetcher > SQLExecutor.
+26- Contributor
Published Parameters can sometimes not work as intended when used within a workspace and I find that it's good practice to first use a ParameterFetcher to put the parameter values into attributes.
In your case, as you're using a SQLCreator, you may need to replace that with a Creator > ParameterFetcher > SQLExecutor.
@nic_ran, I agree that would be a work around.
But I also feel like this should get the attention of Safe, as the transformer SQLCreator should be able to use published parameters.
+16- Contributor
@nic_ran, I agree that would be a work around.
But I also feel like this should get the attention of Safe, as the transformer SQLCreator should be able to use published parameters.
Absolutely agree! Published Parameters should just work everywhere and it seems to be not that uncommon for them not to work as intended. Whenever one of these issues is found it should definitely be brought to Safe's attention - but sometimes we need a workaround until the issue is resolved. :)