Hi @ebygomm! Thanks for posting this! I haven't considered issues with using the Define Read Criteria option. From my understanding of the transformer, the SQL is passed to ArcObjects so the SDE functionality technically shouldn't be bypassed.
What specific SDE functionality you're thinking might be affected? Did you run into a particular issue or see a scenario that might cause problems? It might be good for us to test this out and make the right changes and adjustments!
Initially I noticed that the resolve domains option wasn't respected when using Define Read Criteria.
Then I tested against a feature class that has archiving turned on.
A simple where clause returns just the current feature, using a query in the Define Read Criteria returns both the current and a historic feature.
Thank you for testing that! That's a really important catch about Define Read Criteria bypassing the archiving functionality. I've filed an internal ticket for the team to look into this.
I don't currently have a timeline, but we really appreciate you putting this on our radar! 🙂 If you notice any other issues please feel free to continue sharing those here or in another community post.
[Internal Ref: FMEENGINE-88696]
