[
https://issues.apache.org/jira/browse/FINERACT-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18084225#comment-18084225
]
Francisco Cuandon commented on FINERACT-535:
--------------------------------------------
Hi [~adamsaghy] this issue still happens on Fineract 1.14, I tried updating
Teller1 status on branch1 to Inactive, even with that Fineract does not allows
to create new Teller1 on branch2.
Fineract launchs the following error:
{code:sql}
ERROR: duplicate key value violates unique constraint "m_tellers_name_key"
Detail: Key (name)=(PRINCIPAL TELLER) already exists.
{code}
Can I work on this?
> Allow the same name of teller if its from different branchs
> -----------------------------------------------------------
>
> Key: FINERACT-535
> URL: https://issues.apache.org/jira/browse/FINERACT-535
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Organization
> Affects Versions: 1.8.0
> Reporter: Mexina Daniel
> Priority: Major
> Labels: features, gci, gsoc, p1
>
> For now when you create a teller with the name which already exist even from
> another branch it gives an error of duplicate name
> Think of the institution which have the same format of naming its tellers
> like Teller1, Teller2, etc
> and it has two branches.
> The system should allow to create Teller1 of branch1 and Teller1 of branch2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
