Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: enforce unique GL Account for each 'Bank Account' (backport #39694) #39750

Merged

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 6, 2024

This is an automatic backport of pull request #39694 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

@mergify mergify bot requested a review from deepeshgarg007 as a code owner February 6, 2024 04:00
@mergify mergify bot requested a review from ruthra-kumar as a code owner February 6, 2024 04:00
@ruthra-kumar ruthra-kumar merged commit ae4c907 into version-14-hotfix Feb 6, 2024
11 checks passed
@ruthra-kumar ruthra-kumar deleted the mergify/bp/version-14-hotfix/pr-39694 branch February 6, 2024 10:18
@frappe-pr-bot
Copy link
Collaborator

🎉 This PR is included in version 14.62.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 22, 2024
@barredterra
Copy link
Collaborator

barredterra commented Mar 11, 2024

@ruthra-kumar this is not a refactor, but a breaking change, which should not be backported. For example, it breaks our bank integration, which assumed that a many-to-one mapping from Bank Account to Account is possible.

@ruthra-kumar
Copy link
Member

Many-to-one mapping makes it hard to differentiate transactions between different bank accounts at the ledger level. This has been reported quite often, which led to the validation being added.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants