[
https://issues.apache.org/jira/browse/FINERACT-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Saghy resolved FINERACT-2905.
----------------------------------
Resolution: Fixed
> Entity Data Table Checks / Data Tables: invalid entities in template and
> unclear validation messages
> ----------------------------------------------------------------------------------------------------
>
> Key: FINERACT-2905
> URL: https://issues.apache.org/jira/browse/FINERACT-2905
> Project: Apache Fineract
> Issue Type: Bug
> Components: Data Tables
> Reporter: Foo Developer
> Assignee: Foo Developer
> Priority: Major
> Fix For: 1.16.0
>
>
> # Entity Data Table Checks / Data Tables: invalid entities in template and
> unclear validation messages
> ## Description
> Three backend issues were identified in **Entity Data Table Checks** and
> **Data Tables**:
> 1. The Entity Data Table Checks template advertises entities that do not
> support checks.
> 2. Data Table validation returns a raw message key when a String column has
> no length.
> 3. Entity Data Table Check validation returns unclear and grammatically
> incorrect error messages.
> ## Environment
> * **Environment:** CBS DEV
> * **Portal build:** `c-496230`
> * **Test date:** 05/10/2026
> * **User:** Admin
> * **API base:** `/api/fineract-provider/api/v1`
> ## Bug 1 — Entity Data Table Checks template lists unsupported entities
> `GET /entityDatatableChecks/template` returns entities such as:
> * `m_savings_account_transaction`
> * `m_savings_product`
> * `m_share_product`
> * `m_wc_loan_product`
> * `m_wc_loan`
> However, these entities have no available statuses or data tables in the
> template.
> Attempting to create a check for them results in:
> `400 - The parameter 'status' must be one of [ ]`
> **Expected:**
> The template should only expose entities that support Entity Data Table
> Checks, with their valid statuses and available data tables.
> Alternatively, if these entities are intended to support checks, the template
> should provide valid statuses and the POST request should succeed.
> ## Bug 2 — String column validation returns a raw message key
> When creating a Data Table with a String column without specifying `length`,
> the API returns:
> `Failed data validation due to: must.be.provided.when.type.is.String.`
> **Expected:**
> A user-friendly validation message, for example:
> `Column length is required for String columns (qa_note).`
> The message should be translated/readable and identify the affected column.
> ## Bug 3 — Entity Data Table Check validation message is unclear
> When an action is blocked because a required data table entry is missing, the
> API currently returns:
> `The datatable [QA_DT_Loan] needs to be filled in before the current action
> can be proceeded`
> **Expected:**
> The message should be grammatically correct and clearly describe the required
> action, for example:
> `Please fill in the data table QA_DT_Loan before approving this loan.`
> Where possible, the message should identify the blocked action/entity.
> ## Impact
> * Admins can configure Entity Data Table Checks for entities that cannot
> actually support them.
> * Invalid or incomplete Data Table configurations produce raw/internal
> validation keys.
> * Data Table Check errors are unclear to API and portal users, making
> configuration and troubleshooting difficult.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
