[ https://issues.apache.org/jira/browse/FINERACT-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mihaly Dallos reassigned FINERACT-1910: --------------------------------------- Assignee: Mihaly Dallos > Data Table query - Advanced > --------------------------- > > Key: FINERACT-1910 > URL: https://issues.apache.org/jira/browse/FINERACT-1910 > Project: Apache Fineract > Issue Type: New Feature > Components: Data Tables > Reporter: Peter Santa > Assignee: Mihaly Dallos > Priority: Critical > Labels: BeanSalad > Attachments: dataTableAdvancedFilteringExample.txt > > > h1. Background > FINERACT-1747 > h1. Goal > Have the querying possibilities - that have been developed with FINERACT-1747 > - extended with the following features: > * pagination - similarly to several Fineract API endpoints > * sorting based on given attribute > * filter for closed (greather-than-or-equal, less-than-or-equal) interval in > case of the following typed fields: > ** date > ** date and time > ** number > ** decimal > ** string/text that can be parsed to numeric > * contains search in string and text fields > * exact match for string and text fields > The filtering parameters should be applied with "AND" relation. > h1. Solution Concept > Have the solution concept aligned between > * FINERACT-1910 > * FINERACT-1912 > * FINERACT-1915 > If multiple columns would be used as column filter, it is advisable not to > put this number of query parameters in the url, but in the body, like > graphql. With this, a request would look like: > h3. URL > GET > {{{}url{}}}/datatables/{{{}dataTableId{}}}/query?resultColumns=column3,column6,column4&offset=0&limit=10&sortOrder=desc&orderBy=transaction_date > h3. Body > See the attached [^dataTableAdvancedFilteringExample.txt]. > The filtering parameters should be applied with "AND" relation. > > <Solution Concept to be extended by developers> -- This message was sent by Atlassian Jira (v8.20.10#820010)