From your perspective, how would you want to set these filters? A SOQL query, or something else?
For myself, I want to write SOQL there, though I'd guess many of your target customers will want a point-and-click option. Selecting a list view for that object could be an interesting UX hack that might be worth exploring: there's some Salesforce Labs product that does that.
Salesforce <> Salesforce is not heavily tested... Curious what use case you have in mind?
I've seen a number of configurations for different purposes, the most common one being sandbox data movements.
Management of multiple production orgs gets complex fast, but there are a few places where a tool like this could find a niche: org migrations come to mind. There's often an interim period where you're two way syncing (even though you'd rather not!) before the org being phased out is done.
Comments
For myself, I want to write SOQL there, though I'd guess many of your target customers will want a point-and-click option. Selecting a list view for that object could be an interesting UX hack that might be worth exploring: there's some Salesforce Labs product that does that.
I've seen a number of configurations for different purposes, the most common one being sandbox data movements.
Management of multiple production orgs gets complex fast, but there are a few places where a tool like this could find a niche: org migrations come to mind. There's often an interim period where you're two way syncing (even though you'd rather not!) before the org being phased out is done.
Good luck!
Really helpful on both fronts, thanks for the thoughts. Both the sandbox and migration use cases make a lot of sense.