Does Not Contain filters have been removed?
We've logged into Pipedrive this morning, and realised that a number of our filters are no longer working.
When I check the conditions, it says that "Does Not Contain" filter is no longer available.
Why on earth would you remove this? And why didn't we get any notice of this change???
We rely extensively on our filters, and I have no idea how we're going to work around this change without significant updates to our backend.
I can't fathom why you would make filters so much less useful by removing such an important option.
Answers
-
I'm very much hoping this is a bug not a product decision.
Please reverse ASAP as this breaks major pieces of functionality.
2 -
Hello everyone!
In this case, we had to apply some limits to Filtering for optimal loading speed. Our Knowledge Base article also has info to reflect this. This said, all your old saved filters should be still working as previously, but new ones and editing has new condition limit applied.
0 -
Hi Kreete,
I get that this must create some server load, but can you please confirm that this isn't a permanent change? Surely you couldn't remove something so fundamental to the filtering interface forever?
thanks,
Tom
2 -
Kreete, this has been a filter option for a long time now. It's a standard filter option used by pretty much every application that offers filtering.
For most of our use cases we have no way to work around it. It's insane you'd take this away without properly consulting with customers.
I think you guys seriously need to reconsider the change and find an alternate way of optimising loading speed. It's not worth sacrificing a core piece of functionality over.
It doesn't matter that the old filters will continue to work - we're still screwed the moment we need to update them.
1 -
I was also very surprised to find that "does not contain" is no longer supported. We, like almost everyone else, rely on our filters heavily and for many reasons. There doesn't appear to be ANY workaround for usage inside PipeDrive, and our API functions that use filters would take weeks to update to filter data themselves. Plus we were not notified of this change and it has business-impacting consequences moving forward.
I really hope PipeDrive will take the users' feedback onboard and restore this option.
2 -
I understand the goal was to speed up searches, but Pipedrive's recent changes are hurting our team's productivity and slowing down sales.
The flag is crucial for lead qualification; without it, it's like driving a car without a steering wheel. What's our next step?
Previously, we took 2 minutes to find results. Now, we've been surprised by a negative impact on our team of 40 people, who used the feature daily to individually review deals and determine if they meet specific criteria for better lead qualification.
We currently have 60k open deals and 40 sales reps relying on Pipedrive. Their commissions are tied to achieving sales goals.
Have you explored whether the companies using this filter are on a specific Pipedrive plan? Offering additional filter options from a specific plan seems like an idea. I'm suggesting this because it appears the issue is more related to the funds Pipedrive invests in maintaining its infrastructure.
Considering alternatives, switching to other CRMs seems like the solution.
I'm genuinely disappointed with Pipedrive.
0 -
I understand the goal was to speed up searches, but Pipedrive's recent changes are hurting our team's productivity and slowing down sales.
The flag is crucial for lead qualification; without it, it's like driving a car without a steering wheel. What's our next step?
Previously, we took 2 minutes to find results. Now, we've been surprised by a negative impact on our team of 40 people, who used the feature daily to individually review deals and determine if they meet specific criteria for better lead qualification.
We currently have 60k open deals and 40 sales reps relying on Pipedrive. Their commissions are tied to achieving sales goals.
Have you explored whether the companies using this filter are on a specific Pipedrive plan? Offering additional filter options from a specific plan seems like an idea. I'm suggesting this because it appears the issue is more related to the funds Pipedrive invests in maintaining its infrastructure.
Considering alternatives, switching to other CRMs seems like the solution.
I'm genuinely disappointed with Pipedrive.
0 -
Thank you @Isabel Oliveira for the feedback here. I am sorry this has affected your everyday workflow that much. Our product team has discussed different options before making this decision and also now with all the feedback, are discussing some further steps. Currently the limits stay as they are, but we are trying to see even more what are the obstacles for specific cases and see further from there.
0 -
Thanks for looking into this again - it's a vital feature for our organisation too and without it Pipedrive feels really broken
0 -
@Kreete K Returning the flag feature seems like an option?
1 -
Pipedrive this is the worst, most ridiculous change I have witnessed since using this platform.
Such a major change without notice?
Why can't you fix your systems instead of killing your users.
Removing the "does not contain" from any database is a disgrace, the worst you can do and shows a lack of skill of either the system or the developers... or a lack of care.
I do hope you spend the money we all send you every month to fix this issue ASAP!!!
0 -
Yes, PLEASE re-implement this filter! It is a crucial part of our management of leads and campaigns. We were under the impression this feature was still functioning per usual when continuing to use Pipedrive and now our workflow is being slowed down, which feels counterproductive for what you were trying to achieve. Fully functioning filters with positive AND negative conditions are CRUCIAL.
1 -
I think the same request was submitted here, I suggest all of us need to vote for it to get "does not contain" filter back), The more people vote the more likely they will return, I definitely used this all the time
1
