Skip to content

IMPORT_SETTINGS_GUIDE.md

Latest commit

 

History

History
250 lines (187 loc) · 7.62 KB

IMPORT_SETTINGS_GUIDE.md

File metadata and controls

250 lines (187 loc) · 7.62 KB

Import Settings Memory

Overview

The Transaction Manager now remembers your import settings for each CSV file. This means you configure once and reuse the settings every time you import that file!

How It Works

First Time Importing a File

  1. Select download.CSV for import
  2. Configuration dialog opens with all checkboxes unchecked
  3. Configure settings:
    • Skip lines: 0
    • Hash columns: ☑ Date, ☑ Description, ☑ Amount Debit, ☑ Amount Credit
  4. Click "Import"
  5. Settings are automatically saved to import_settings.json

Second Time (And Every Time After)

  1. Select download.CSV again
  2. Configuration dialog opens with:
    • ✓ Loaded previous settings for this file (message at top)
    • Skip lines: 0 (remembered!)
    • Hash columns: ☑ Date, ☑ Description, ☑ Amount Debit, ☑ Amount Credit (remembered!)
  3. Options:
    • Click "Import" immediately (use saved settings)
    • Adjust settings if needed, then click "Import" (new settings will be saved)

Settings Storage

Location

Settings are stored in: import_settings.json

Format

{
  "download.csv": {
    "skip_lines": 0,
    "hash_columns": ["Date", "Description", "Amount Debit", "Amount Credit"],
    "available_columns": ["Transaction Number", "Date", "Description", "Memo", ...],
    "last_used": "2025-10-12T14:23:45.123456"
  },
  "export.csv": {
    "skip_lines": 2,
    "hash_columns": ["Date", "Merchant", "Amount"],
    "available_columns": ["Date", "Merchant", "Amount"],
    "last_used": "2025-09-15T10:11:12.654321"
  }
}

Key Features

Per-File Settings:

  • Each CSV filename has its own settings
  • download.CSV settings are separate from Export.csv settings
  • Case-insensitive (DOWNLOAD.CSV = download.csv)

What's Saved:

  • Number of lines to skip
  • Which columns to use for duplicate detection
  • All available columns (for reference)
  • Last used timestamp

What's NOT Saved:

  • Debug mode checkbox (always starts unchecked)
  • File path (only filename is used as key)

Examples

Example 1: Monthly Bank Exports

You download monthly exports from your bank:

  • October2025.csv
  • November2025.csv
  • December2025.csv

First file (October):

  • Configure: Skip 0, use Date+Description+Amount
  • Import completes
  • Settings saved as "october2025.csv"

Second file (November):

  • Same filename pattern? No settings loaded (new filename)
  • Configure again: Skip 0, use Date+Description+Amount
  • Import completes
  • Settings saved as "november2025.csv"

Next month's October file:

  • If you name it October2025.csv again → Settings remembered!
  • If you name it October2026.csv → New file, configure again

Example 2: Different Bank Accounts

You have multiple bank accounts:

  • Checking: exports as checking_export.csv
  • Savings: exports as savings_export.csv

Checking account:

  • Configure: Skip 0, use Date+Description+Amount Debit+Amount Credit
  • Settings saved for "checking_export.csv"

Savings account:

  • Configure: Skip 2, use Date+Merchant+Amount
  • Settings saved for "savings_export.csv"

Each file remembers its own specific settings!

Example 3: Renaming Files

If you rename files, settings are based on the NEW name:

download.CSV → Settings saved as "download.csv"
Rename to: transactions_oct.csv → Settings NOT found (different name)
Rename back to: download.CSV → Settings loaded! ✓

Tip: Use consistent filenames to benefit from saved settings.

User Interface Indicators

When Settings Are Loaded

┌─────────────────────────────────────────────┐
│ ✓ Loaded previous settings for this file   │  ← Green message
│                                             │
│ Check the columns to use:                  │
│ ☑ Date  ☑ Description  ☑ Amount Debit ...  │  ← Pre-checked!
│                                             │
│ 💡 Using previously saved column selection │
│    (Change if needed, or click Import...)  │
└─────────────────────────────────────────────┘

When Settings Are NOT Found

┌─────────────────────────────────────────────┐
│ Check the columns to use:                  │
│ ☐ Date  ☐ Description  ☐ Amount Debit ...  │  ← All unchecked
│                                             │
│ 💡 Recommended: Check Date, Description... │
│    (You must select at least one column)   │
└─────────────────────────────────────────────┘

Advanced Usage

Viewing Saved Settings

Open import_settings.json in a text editor to see all saved settings:

notepad import_settings.json     # Windows
cat import_settings.json          # Mac/Linux

Clearing Settings

For One File: Manually edit import_settings.json and remove that file's entry.

For All Files: Delete import_settings.json and restart. All settings forgotten, start fresh.

Sharing Settings

Copy import_settings.json to another computer:

  • Settings will work if CSV filenames match
  • Useful for multiple users with same bank exports

Benefits

1. Save Time

Configure once, reuse forever. No need to remember which columns to check.

2. Consistency

Same file always uses same settings. Reduces errors.

3. Multiple Banks/Sources

Each CSV source has its own configuration automatically.

4. Flexibility

Can still change settings anytime. New settings are saved automatically.

5. No Manual Management

Everything is automatic. Just import and settings are saved.

Troubleshooting

Q: Settings not loading?

A: Check the filename. Settings are based on the filename, not path.

  • C:\Downloads\export.csv → Key: "export.csv"
  • D:\Backups\export.csv → Same key: "export.csv" ✓

Q: Want different settings for same filename?

A: Rename one of the files:

  • export.csv → Use settings A
  • export_v2.csv → Use settings B

Q: Settings from wrong file loading?

A: Files with same name share settings. Rename files to be unique:

  • bank1_export.csv
  • bank2_export.csv

Q: Want to reset all settings?

A: Delete import_settings.json, restart app.

Q: Can I edit settings manually?

A: Yes! Edit import_settings.json in a text editor. Valid JSON format required.

Technical Details

Storage Format

  • File: import_settings.json
  • Encoding: UTF-8
  • Format: JSON dictionary
  • Key: Lowercase filename (no path)
  • Auto-created: On first import
  • Auto-saved: After every successful import config

Filename Normalization

"C:\Users\brian\Downloads\Export.CSV" → "export.csv"
"/home/user/docs/Export.CSV" → "export.csv"
"D:\Bank\EXPORT.csv" → "export.csv"

All map to the same settings key!

Column Matching

When loading settings, columns are matched by exact name:

  • Saved: ["Date", "Description"]
  • Current CSV has: ["Date", "Description", "Memo"]
  • Result: ☑ Date, ☑ Description, ☐ Memo

If a saved column doesn't exist in current CSV, it's ignored.

Summary

✓ Configure once per filename ✓ Settings automatically saved ✓ Settings automatically loaded ✓ Change anytime, new settings saved ✓ Per-file settings (different files = different settings) ✓ Visual indicator when settings are loaded

No manual management needed - just import and the system remembers!