Consider null values when using NOT_IN filte
in progress
Q
Quartz Squid
As of now When we apply the NOT_IN filter on any field, we only consider the non-null values which makes the perspective drop the costs under No product.
The ER is to consider null values when using NOT_IN filter
Log In
This post was marked as
in progress
E
Excellent Stork
next fiscal quarter
Q
Quartz Squid
This effectively breaks the ability for Harness to be accurate if a customer has an EDP and uses a NOT_IN or IN filter, because the EDP discount is not associated to a product name. This creates an added problem because there's a discount toggle already that is supposed to handle this-leading to an issue where the customer can't actually check it.
E
Excellent Stork
under review