[
https://issues.apache.org/jira/browse/FINERACT-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17776703#comment-17776703
]
Peter Santa commented on FINERACT-1911:
---------------------------------------
h3. Márta Jankovics
August 17, 2023 at 8:45 PM
Exception handling is inconsistent for the datatable actions. I have not
changed it yet, so would like to record it for further improvements.
Most of the validation errors return 400, but there are validations that return
different response codes:
* 500:
deleteDatatable: datatable is not empty, datatable is not registered
updateDatatable: non-empty column can not be deleted, datatable is not
registered
createNewDatatableEntry, createPPIEntry: datatable is not registered
getDatatableEntries: datatable is not registered
updateDatatableEntry: entry does not exist, multiple entries exist, datatable
is not registered
deleteDatatableEntries: datatable does not exist, entry does not exist,
datatable is not registered
* 503:
updateDatatable: rename column name is not valid, one of the data table columns
contains null values
* 403:
createDataTable : invalid datatable name, datatable is not supported for the
requested type
registerDataTable : datatable already registered
updateDatatable: provided column name does not exist, non empty datatable
mandatory columns can not be added, datatable does not exist
createNewDatatableEntry, createPPIEntry: unique entry violation, mandatory
field is not provided, main entity does not existupdateDatatableEntry: main
entity does not exist
getDatatableEntries: main entity does not exist
deleteDatatableEntries: main entity does not exist
> Assign Data Table to Transaction (Savings)
> ------------------------------------------
>
> Key: FINERACT-1911
> URL: https://issues.apache.org/jira/browse/FINERACT-1911
> Project: Apache Fineract
> Issue Type: New Feature
> Components: Data Tables
> Reporter: Peter Santa
> Assignee: Muthu
> Priority: Major
> Labels: BeanSalad
> Fix For: 1.9.0
>
>
> h1. Background
> Currently data tables can be assigned to several entity types, but
> transaction is not an option.
> h1. Goal
> The context is mainly Transactions of {*}Saving Accounts{*}, but it would be
> great to implement the feature generally.
> The goal would be to make it possible to
> * {*}assign data table to transactions{*}, and
> * support multi-row and single-row tables - as it is already supported for
> data tables that could be assigned to other entities.
> h1. Acceptance Criteria
> * it is supported to assign *data tables to Transaction entities* of - at
> least - savings accounts, and the solution fits into the current data table
> conception
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
