+43Hello FME friends.
Here is a video recording of Dan and I answering your recent questions about dynamic workflows. I hope you find it useful and/or interesting.
I apologize for the poor video quality of my side of the conversation. It’s my first time recording a meeting like this. I hope to sort it out for future recordings.
+27Thanks Mark and Dan! I really appreciate taking the time and love the AMA 😀
+17Thanks for joining us on the community
+28The thing I find really annoying about the FeatureReader is that when the workspace is dynamic and the dataset is set to an attribute, then every single time I edit a parameter, even one that doesn’t affect the dataset, (ex. Merging attributes with the initiator feature) , I get the pop-up box about having to use the generic port, or browse to an existing dataset to rescan the schema. This occurs even when the format has a fixed schema (ex geotiffs).
90% of the time when I’m using the featureReader it’s for dealing with tiled data. The workflow is reading in an Area of Interest Polygon, intersect it against an index polygon file that has the path to the individual files as an attribute and then a FeatureReadure with that attribute as the source. It would be really nice if I could just scan the schema once, and then not have to deal with it again unless I specifically tell it to update, the same as regular reader feature types.
+43
I asked for that one because I, too, kept being annoyed; especially when I used a local file for testing then needed to change the path to $(FME_SHAREDRESOURCE_DATA) for publishing to Flow. It would try to update the schema and fail because it couldn’t find the path locally!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
