[
https://issues.apache.org/jira/browse/FINERACT-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Santa updated FINERACT-1916:
----------------------------------
Description:
h1. Background
Data Table related querying has been enhanced with FINERACT-1747 and
FINERACT-1910, FINERACT-1915.
The result set currently does not say anything about the data type.
h1. Goal
If the caller requests that way (advancedResultSet=true), let the result set of
* data table query
* parts of Transaction query that includes data from data table (FINERACT-1915)
include data type related information, and have a response that is similar to
the response of a table Report.
h4. Example response
As a report response look like for this request, utilising a built-in report:
{{{}url{}}}/runreports/Client%20Listing?R_officeId=1
Let the caller customise in the request whether the currently existing simple,
or the advanced result set format is required.
h1. Solution Concept
Have a flag in the request: advancedResultSet=true to let the caller configure,
that advanced (reporting-like) result set is requested.
<Solution Concept to be extended by developers>
h1. Acceptance Criteria
* The result set of a data table query looks like the response of a report,
including types of values in columns.
was:
h1. Background
Data Table related querying has been enhanced with FINERACT-1747 and
FINERACT-1910, FINERACT-1915.
The result set currently does not say anything about the data type.
h1. Goal
If the caller requests that way (advancedResultSet=true), let the result set of
* data table query
* parts of Transaction query that includes data from data table (FINERACT-1915)
include data type related information, and have a response that is similar to
the response of a table Report.
Example response: as a report response look like for this request, utilising a
built-in report:
{{{}url{}}}/runreports/Client%20Listing?R_officeId=1
Let the caller customise in the request whether the currently existing simple,
or the advanced result set format is required.
h1. Solution Concept
Have a flag in the request: advancedResultSet=true to let the caller configure,
that advanced (reporting-like) result set is requested.
<Solution Concept to be extended by developers>
h1. Acceptance Criteria
* The result set of a data table query looks like the response of a report,
including types of values in columns.
> Data Table query - Advanced result set
> --------------------------------------
>
> Key: FINERACT-1916
> URL: https://issues.apache.org/jira/browse/FINERACT-1916
> Project: Apache Fineract
> Issue Type: New Feature
> Components: Data Tables
> Reporter: Peter Santa
> Priority: Major
> Labels: BeanSalad
>
> h1. Background
> Data Table related querying has been enhanced with FINERACT-1747 and
> FINERACT-1910, FINERACT-1915.
> The result set currently does not say anything about the data type.
> h1. Goal
> If the caller requests that way (advancedResultSet=true), let the result set
> of
> * data table query
> * parts of Transaction query that includes data from data table
> (FINERACT-1915)
> include data type related information, and have a response that is similar to
> the response of a table Report.
> h4. Example response
> As a report response look like for this request, utilising a built-in report:
> {{{}url{}}}/runreports/Client%20Listing?R_officeId=1
>
> Let the caller customise in the request whether the currently existing
> simple, or the advanced result set format is required.
> h1. Solution Concept
> Have a flag in the request: advancedResultSet=true to let the caller
> configure, that advanced (reporting-like) result set is requested.
> <Solution Concept to be extended by developers>
> h1. Acceptance Criteria
> * The result set of a data table query looks like the response of a report,
> including types of values in columns.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
