Skip to content

Improvement: IBFlex allow re-marking "OK" entry for import#5534

Open
georgemac-labs wants to merge 1 commit intoportfolio-performance:masterfrom
georgemac-labs:improvement/ibflex-import-flag-reactivatable
Open

Improvement: IBFlex allow re-marking "OK" entry for import#5534
georgemac-labs wants to merge 1 commit intoportfolio-performance:masterfrom
georgemac-labs:improvement/ibflex-import-flag-reactivatable

Conversation

@georgemac-labs
Copy link
Contributor

I noticed in the IBFlex process you can right-click to mark an "OK" transaction as "Do not import" but you cannot then revert that flag! That seems like a gap to me.

After right-clicking and setting a valid entry as "Do not import",
make it possible to revert it to "Import".
Comment on lines -665 to +667
|| (!entry.isImported() && (entry.getMaxCode() == Code.WARNING));
|| (!entry.isImported() && (entry.getMaxCode() == Code.WARNING
|| (entry.getMaxCode() == Code.OK && entry.isExplicitlyNotImported())));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. But couldn't we simplify even further:

If it the item
a) is currently not imported AND
b) it could be imported (e.g. the maxcode is WARNING or OK)
then the user can change the decision.
If it is FAILURE, of course, the user cannot make that decision. Same is true for SKIP (= transactions not supported by PP)

            atLeastOneNotImported = atLeastOneNotImported || (!entry.isImported()
                            && (entry.getMaxCode() == Code.WARNING || entry.getMaxCode() == Code.OK));

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so, because user choice is not the only reason that entry.isImported() can be false – it includes a dependency check.

So if you decide based on maxCode, the app might allow the user to explicitly mark an entry to be imported, but then it won't be. I think that's a less good UI.

Copy link
Contributor Author

@georgemac-labs georgemac-labs Mar 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incidentally, I would say this area is slightly muddled. There are two questions: whether the entry CAN be imported and whether the user WANTS it imported.

The concept seems to be that "can" is represented by maxCode and the icon.

However, a piece of "can" has ended up mixed up with "want" in the code (isImported()), which is presumably what misled you into thinking the code could be simpler. And it's leaked into the UI, too, using strikethrough for both user choice AND for entries blocked by failed dependencies.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@buchen did I address your comment? Anything further to do to get this merged?

@buchen buchen added the bug label Mar 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants