Skip to content
This repository has been archived by the owner on Dec 13, 2020. It is now read-only.

Combined Filter Functionality #1021

Closed
metas-mk opened this issue Jul 13, 2017 · 10 comments
Closed

Combined Filter Functionality #1021

metas-mk opened this issue Jul 13, 2017 · 10 comments

Comments

@metas-mk
Copy link
Member

metas-mk commented Jul 13, 2017

Type of issue

Feature request

Current behavior

Currently, if there are different Filters in a Window, only 1 Filter can be used at a time. Setting the first filter and then recording the 2nd leads to an "initialization2 of the 1st one.

Expected behavior

Allow the user to set different Filter criteria and filter the data by the combination of Filters.

Example test case for multi Filter window: https://w101.metasfresh.com:8443/window/143

image

@wiadev
Copy link
Contributor

wiadev commented Aug 22, 2017

@metas-mk Right now, it's done exactly as stated in issue. However technically no problem to make even more than 2 filters. If you want this - please create a new issue.

@wiadev
Copy link
Contributor

wiadev commented Aug 22, 2017

I found an issue, though.
screenshot at aug 22 19-26-36

Unde Partner and Date ordered, we have another Date filter and both of Date filter from 1st and 2nd filter are pointing same field.

at this point, I think we should remove the date filter from Partner and Date ordered.
FYI, date filter from Partner and Date ordered are returning from the backend config. you should remove it over there if you want.

@wiadev
Copy link
Contributor

wiadev commented Aug 22, 2017

In fact I wanted to propose to extend this feature ever further

my proposal as following:

  1. we can have ONE button initally - filter which shows dropdown with all possible filters (of course when filters are already applied and we're refreshing the page - it will restore all applied filters)
  2. when user selects one filter - we're making this button blue (indicating it's of active state) and add another filter button (which will have dropdown list of possible filtering options, except of already applied filter). This repeats until we have any filters left
  3. to remove any of pieces from filter - you just click on blue button and then click "Clear filter" to remove this part

benefits:

  1. No need in two component - Frequent filters and Non-frequent, which are quite overlapping by code. So we can reduce amount of involved code
  2. We will be able to have more than 2 filters applied simultaneously

@teosarca
Copy link
Member

@wiadev about "Partner and date" filter.

Quick checked and for me looks ok. See the screenshot below. Remark the value and valueTo fields.

Can you point me more precisely where is the error?

image

@wiadev
Copy link
Contributor

wiadev commented Aug 23, 2017

@teosarca no, there is no error but we have 2 date filters in both of 1st(Filter by Date) and 2nd (Filter: Partner and Date ordered)

since we are using combined filter I don't think we need another date filter under Partner and Date ordered from 2nd Filter.

@metas-mk
Copy link
Member Author

metas-mk commented Aug 23, 2017

@wiadev

@metas-mk Right now, it's done exactly as stated in issue. However technically no problem to make even more than 2 filters. If you want this - please create a new issue.

No that's not right. The issue describes the initialization of the first set filter after using another second filter.
What is meant with filter? Filter Buttons (see the screenshot and the red arrows showing to them)

Please ping me when you have time and I can describe via screen session.

EDIT: Ah, I see that you've already created a PR but it's not merged yet. Let me merge and check first and I will come back with more info.

metas-mk added a commit that referenced this issue Aug 23, 2017
Implement composite filter support for DocumentList #1021
@teosarca
Copy link
Member

no, there is no error but we have 2 date filters in both of 1st(Filter by Date) and 2nd (Filter: Partner and Date ordered)

since we are using combined filter I don't think we need another date filter under Partner and Date ordered from 2nd Filter.

@wiadev ahhh, now i got it.
Yes, from a logical point of view, you are right but the thing is that those filters can be easily defined by a system admin. So in this case that filter is more a test case used to validate frontend.

@wiadev
Copy link
Contributor

wiadev commented Aug 24, 2017

@teosarca this is already on branch:master. should I put the label and assign back to you?

@teosarca
Copy link
Member

@wiadev thx for reminder, just did it

@metas-lc
Copy link

IT
used Date filter and a filter from default (e.g. bpartner) and worked fine, together. OK

metas-ts added a commit to metasfresh/metasfresh that referenced this issue Aug 27, 2017
[#1021](metasfresh/metasfresh-webui-frontend-legacy#1021)
Combined Filter Functionality
[1140](metasfresh/metasfresh-webui-frontend-legacy#1140)
Lookup Workflow for Batch Entry not correct
[#1150](metasfresh/metasfresh-webui-frontend-legacy#1150)
error reappears after you changed window
[#546](metasfresh/metasfresh-webui-api-legacy#546)
Notification Deleting
[#2231](#2231) Add Import
Partner and Product Processes Available in Import Windows
[#2136](#2136) add
history to B2C window
[#2109](#2109) Move
Currency Records from System to Client level so user can edit them
[#2103](#2103) Create and
implement the usage of a pdf printer
[#2116](#2116) Use
handler when matching partner in ESR import
[#2036](#2036) Picking
Slot Label
[#2142](#2142) Customer
Returns error w/ create from Shipment in WebUI

me-45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants