I've been live testing the Product flows and found some irregularities with the construct, considering they use the same Saved Search as the soon-to-be deprecated flows. I might not understand why entirely, but a jump from the REST API to GraphQL might be better served without using existing Saved Search for a new one - albeit based on the old one, especially for this type of testing. Thoughts?
1 Like
Agree, and I told them as much - as well as the settings for full/delta flows that copy across the old and new flows. I want to be able to test with a saved search filtered to a single item (or very limited set of items) and run it as "All - always export all data" export type, while the REST flow continues running for the full set of products as normal. They've really made testing GraphQL impossible while you're still trying to be live on REST.
As a work around to test on single items (or multiple by putting multiple filter rules and using OR), you can add input filters to the "Post products to Shopify" and "Delete metafields in Shopify" bubbles. Adding filters here does not impact the REST flows.
I like this, but since staff have needed to modify the initial Saved Search with formulas (especially for Matrix) for GraphQL, not for REST API, this technique you provide does not account for that. Again, IMHO decoupling the Saved Search from the GraphQL eliminates the need to "filter" and also provides for continued use of existing functionality while testing the new flow.
@gabeparr I agree they should be different. Checking with @nileshkumar to see if this is even feasible to do at this point.