Bug: Duplicate Import Mapping when going back/forth in steps

[HStep20]

Before you start (required)

General checklist

• I have removed personal / sensitive data from screenshots and logs
• I have searched existing issues and discussions to ensure this is not a duplicate issue

How are you using Maybe?

• I am a self-hosted user

Self hoster checklist

Paying, hosted users should delete this entire section.

If you are a self-hosted user, please complete all of the information below. Issues with incomplete information will be marked as Needs Info to help our small team prioritize bug fixes.

• Self hosted app commit SHA (find in user menu): [enter commit sha here]
  • I have confirmed that my app's commit is the latest version of Maybe
• Where are you hosting?
  • Render
  • Docker Compose
  • Umbrel
  • Other (please specify)

---

Bug description

When using the import, its possible to cause Duplicate Accounts to show up on the mapping screen

To Reproduce

Be as specific as possible so Maybe maintainers can quickly reproduce the bug you're experiencing.

1. Start an import
2. upload a CSV
3. Set up the config for columns
4. Hit Next until you are on the 'Map' tab
5. Map 1-all of your accounts to an account type
6. Go back to the Configure tab
7. Edit a configured value
8. Return to the Map tab
9. Youll see all values that were initially configured are still there, alongside duplicate versions of the accounts.

Attempting to map these duplicate accounts to columns results in the dropdown being reset to its default state, breaking the current import completely.

---

As an aside, some more info on what the dropdowns on the 'configure' tab actually mean would be invaluable. Importing from Actual, and I have no idea what an 'Entity Type' means in this context, or the Name.

Ah, I understand now that Account imports are different than Transaction imports. It seems like Transaction imports are hidden until an account exists, but I might recommend not doing this, as you are forced to apply each account to an existing one or are given the open to create it during the Transaction Import Workflow.

Obscuring this feels like bad UX and might lead to situations like I experienced where I thought I was importing transaction with the only import that was available, and only later found out that I was supposed to import accounts via the import workflow