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]: "Select values": Button "Get fields to select" not working when there are already fields listed #3142

Closed
gertwieland opened this issue Aug 5, 2023 · 4 comments
Labels

Comments

@gertwieland
Copy link

gertwieland commented Aug 5, 2023

Apache Hop version?

2.5

Java version?

openjdk 11.0.19 2023-04-18 OpenJDK Runtime Environment OpenLogic-OpenJDK (build 11.0.19+7-adhoc..jdk11u) OpenJDK 64-Bit Server VM OpenLogic-OpenJDK (build 11.0.19+7-adhoc..jdk11u, mixed mode)

Operating system

Windows

What happened?

The "Get fields to select" button in the "Select values" transform works fine when no fields are listed yet (eg. when using the transform for the first time).

However, it doesn't work when the list is already populated. At this point, pushing the button (for example because the incoming fields have changed) does nothing.

After deleting the current fields manually and then hitting that button again, it states that "There already is data entered, 0 lines were found".

It seems that at this step, it recognizes that there WERE fields before, but then it counts the current fields and finds that there are zero.

image

And just since we are on it, maybe change (shorten) the message to: "X fields are listed already." (e. g. 7 fields are listed already).

EDIT: I noticed that when the list is basically the same but there are just additional incoming fields, it just adds them without asking "how" they should be added (i.e. the popup in the screenshot above doesn't show up).

Issue Priority

Priority: 3

Issue Component

Component: Hop Gui

@hansva
Copy link
Contributor

hansva commented Aug 5, 2023

Thanks for reporting this @gertwieland! This has been fixed with #3020

@hansva hansva closed this as completed Aug 5, 2023
@hansva hansva added this to the Not Applicable milestone Aug 5, 2023
@gertwieland
Copy link
Author

Thanks a lot, @hansva. I think the JavaScript transform has basically the same (or similar) issue..
I still didn't get to pull and test 2.6. Would you know if that too has been fixed?

@hansva
Copy link
Contributor

hansva commented Aug 6, 2023

It's an issue in all transforms with that button in 2.5. It has been solved globally.

@gertwieland
Copy link
Author

gertwieland commented Aug 6, 2023 via email

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

No branches or pull requests

2 participants