[
https://issues.apache.org/jira/browse/FINERACT-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732832#comment-17732832
]
Muthu commented on FINERACT-1911:
---------------------------------
[~jdailey]
Currently, we capture transactions using a fixed set of attributes. However, as
mentioned by [~peter.santa] there may be cases where additional
transaction-related attributes are required, such as debtorIban, creditorIban,
correlationId, and settlementDate. Adding these attributes directly to the core
Transaction entity may not be the most flexible and maintainable solution, as
it can lead to data model modifications and potential compatibility issues.
Assuming that the additional transaction related attributes will be limited in
number and not over complex, I would like to propose implementing a flexible
schema approach using the concept of {{{}additionalAttributes{}}}. By
introducing a {{Map<String, Object>}} field named {{additionalAttributes}}
within the Transaction entity, we can dynamically capture and store any
additional attributes specific to each transaction. This approach allows us to
accommodate custom attributes without modifying the core data model, ensuring
data integrity and simplicity.
While the proposed flexible schema approach is simpler, I want to highlight a
potential challenge related to filtering capabilities based on the additional
attributes. If we anticipate the need for advanced and dynamic filtering
functionality, the datatable approach might be more suitable as datatable
approach provides a structured and indexed database table specifically designed
for storing dynamic attributes.
I welcome thoughts and suggestions on this proposed approach.
Thanks
> 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
> Priority: Major
> Labels: BeanSalad
>
> 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)
