Agreed! The behavior should be consistent with data designer / HRE in Connectors (at all levels). 

@anirbandutta may you be so kind as to tag in the appropriate product manager here? “Expected behavior” is frankly a copout response here. What is the point in being able to preview job data if it doesn’t honor your filters?? Just because it may have been an oversight when they designed the solution doesn’t make in contextually inaccurate. This should be considered a bug.

+1, ran into this at the end of 2023.  A preview is supposed to be an insight into the output data, this is how it works in Bionic/Horizon, right? Previewing in connectors should follow the same behavior.  Support or Product may be classing this as expected behavior - as an end user I can confirm adding filters and they’re ignored in preview is NOT expected behavior.

This may not be along the same lines, but…

It feels like this is how queries (in advanced JO’s, curious how they’ll work in dynamic JO’s) work. And it’s one of the reasons queries make audience building so easy in comparison to segments. Previewing and seeing “no records for the given configuration” is a quick way to tell that we’ve got to make an adjustment to our filters.

Wishlist here… it’d be AWESOME to eventually be able to get an indication in the preview of the total number of participants that would be brought in with the current filter setup. If I need to submit that as an idea, I definitely can.

Yes, please make the filtering preview for the connector work the way it does in Horizon. Didn’t see this post first so opened a ticket. An accurate preview would have saved us both time.

I ran into this issue again today
According to this response in Hardik’s idea linked above there are some challenges to support filters in the SF connector, but those limitations are not mentioned anywhere else.

Is it possible to at least add a warning to give context about these limitations when using connectors + filters? A pop-up when adding a filter for example? Updating the documentation to include this would be great too.

Hi Team,

This is causing an issue for us. It should be consistent with data designer and Rules. 

Please maintain consistency or explicit show warnings or banners to inform filters are not respected. Anyone from Ops would want this to be upvoted.

@revathimenon can we have someone from product confirm the latest on this? Appreciate if you can relay this internally.

Hi All, Thank you for your suggestion!
Currently, to view the filtered data, you need to view logs under the activity tab for the job, where you can see the data from the downloaded file. The reason we don't provide this earlier is that external systems' APIs differ; some offer filtering capabilities, and some do not. The data preview in connectors is meant to check if data is coming in for the fields you've selected and help you prepare jobs. However, we will try to add this functionality for external systems that support filtering in the future.

Hi @inagar -- in the short term, can we consider adding new header text to the Preview window for SFDC Connector?  New Admins (and even more seasoned admins who just have missed this at some earlier time) regularly open tickets around this, since “Preview” in DD and Rules Engine look the same, leading to assumption that correctly-filtered data will be shown here as well.

I think it should remain on the “must fix” list as well - it isn’t a preview if it shows data that doesn’t actually meet the query setup - but I know that will take longer - in the meantime, a lot of frustration can be avoided with a new message (see my screenshot below).  Thanks!

+1 This is one of the most important areas for filters and preview to show correctly before implementing.