I have a workbench which is calling data back for 8 reports via 8 different httpcallers. I can add a date parameter to the URL to call back one date at a time. I have 60 dates I need to individually grab the data for.
How can I get it too complete the workbench, move on a day and run it again, and again...and so forth, through a list of dates?
Solved
Workbench has a number of HttpCallers that need running for each of a series of dates
+4- Contributor
Best answer by redgeographics
If you have a list of those dates as say a text file (one date per line) or Excel you can read that in. Each date then becomes a feature, with that date as the attribute. Use that to feed your HTTPCallers.
You’re potentially going to run into rate limiting issues, if that’s the case, a more elegant solution would be to use your original workspace but make a User Parameter for the date (if you haven’t done so already) and create a second workspace that reads the list of dates, then runs your original workspace using a WorkspaceRunner, which you can set to “wait for job to complete”, so it only runs one date at a time. In the WorkspaceRunner you’ll get access to the user parameters of the original workspace, so you can feed it the date attribute.
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.
+61- Celebrity
- Best Answer
If you have a list of those dates as say a text file (one date per line) or Excel you can read that in. Each date then becomes a feature, with that date as the attribute. Use that to feed your HTTPCallers.
You’re potentially going to run into rate limiting issues, if that’s the case, a more elegant solution would be to use your original workspace but make a User Parameter for the date (if you haven’t done so already) and create a second workspace that reads the list of dates, then runs your original workspace using a WorkspaceRunner, which you can set to “wait for job to complete”, so it only runs one date at a time. In the WorkspaceRunner you’ll get access to the user parameters of the original workspace, so you can feed it the date attribute.
FME rocks! \m/
+45- Influencer
Clone the initial feature 60 times and then create the date parameter using by adding the clone number of days to the starting date. Then send all these into your http callers, you probably want to consider a decelerator to limit the rate of requests
+4- Contributor
If you have a list of those dates as say a text file (one date per line) or Excel you can read that in. Each date then becomes a feature, with that date as the attribute. Use that to feed your HTTPCallers.
You’re potentially going to run into rate limiting issues, if that’s the case, a more elegant solution would be to use your original workspace but make a User Parameter for the date (if you haven’t done so already) and create a second workspace that reads the list of dates, then runs your original workspace using a WorkspaceRunner, which you can set to “wait for job to complete”, so it only runs one date at a time. In the WorkspaceRunner you’ll get access to the user parameters of the original workspace, so you can feed it the date attribute.
Thank you, this second method was perfect