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

[Bug Report] Error in reports when consulting search criteria "Bank Account" and "Currency" #782

Closed
oscarinak opened this issue Apr 23, 2021 · 0 comments
Labels
02 Bug Something isn't working 34-Legacy Very old, not been addressed for a long time

Comments

@oscarinak
Copy link
Collaborator

Bug report

The following error occurs with the search criteria of "Bank Account" where when consulted in some reports that have this search criteria, it does not show any information and when displaying it only remains processing, because in ADempiere-Vue it is as a list type field and not as it was before it was a search type field.

On the other hand, the search criteria "Currency", when consulted or used in some reports, shows all the currencies created in ADempiere even when some currencies are already inactive, and previously in the other ADempiere this if validated.

The reports that present this problem are the following:

  • Balance in Banks
    -Account Status Report
  • Payment details

Steps to reproduce

The step by step for this case is to enter ADempiere-Vue and verify each of the reports that are being discussed in this issue

Screenshot or Gif(截图或动态图)

Link to minimal reproduction(最小可在线还原demo)

https://demo-ui.erpya.com/

Expected behavior

The expected result for this case is that when consulting the search criteria "Bank Account" it shows the information of the bank accounts created in ADempiere that are active.
In the case of the "Currency" search criterion, it is that it validates and shows only the currencies that are active in ADempiere

@oscarinak oscarinak added the 02 Bug Something isn't working label Apr 23, 2021
@marcalwestf marcalwestf added the 34-Legacy Very old, not been addressed for a long time label Feb 3, 2025
@marcalwestf marcalwestf closed this as not planned Won't fix, can't repro, duplicate, stale Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
02 Bug Something isn't working 34-Legacy Very old, not been addressed for a long time
Projects
None yet
Development

No branches or pull requests

2 participants