[ https://issues.apache.org/jira/browse/FINERACT-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Santa updated FINERACT-1910: ---------------------------------- Description: 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) and open (greater-than, less-than) 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 h1. Solution Concept 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. 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. was: 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) and open (greater-than, less-than) interval in case of the following typed fields: ** date ** date and time ** number ** decimal ** string/text that can be parsed to numeric * "LIKE" search in string and text fields * exact match for string and text fields h1. Solution Concept 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. 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. > Have advanced features for data table querying > ---------------------------------------------- > > 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 > Priority: Critical > 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) and open > (greater-than, less-than) 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 > h1. Solution Concept > 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. 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)