Currently to use the batch deploy option the workspace must have a writer. If there is not one, the option is greyed out. Given that are multiple ways to create data via transformers, this restriction no longer makes sense.
Archived
Batch Deploy should not require a writer
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- Contributor
Interestingly enough, all you need is a writer, it doesn't have to be attached to anything or even enabled.
+10- Contributor
Currently a Reader & Writer is required to enable the batch deploy, but as mentioned by jdh, there are also other ways to read data.
As mentioned; the work around is to add a Reader & Writer that do nothing.
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.