Originally Posted by
b12e
I get that, but the export PDF does contain the "correct actual" state (amount of XP, amount of miles, amount of UXP), so perhaps as a kickstart it should go from "current state" and look back, rather than start from the bottom and work up. There's, realistically speaking, no way for me to "fix" the balance besides manually add an entry with a fake flight number to "correct" the data.
There should also be events to indicated requalifications, so I guess getting the correct qualification period should also be possible automatically without manual intervention (e.g. the below screenshot).
Either way I've been platinum for longer than the PDF export, so getting old data is going to be near impossible (I do have the flights logged in Flighty, but not the XP and miles movements), perhaps the import should only consider "complete" data, in my case 2023 and newer (since the first "XP Counter offset" in the data) - and warn that older data needs to be manually added.
Really good points. You’re touching on exactly the limitations of the current approach.
Working backwards from current state: you’re right that the PDF header contains your actual XP/Miles/UXP balance. Using that as the truth and reconciling backwards would be smarter than building up from incomplete history. I should have thought about that one.
Auto-detecting qualification period: also a great catch. The requalification events in the PDF could indeed be used to automatically set the correct cycle. Will fix that too.
Incomplete historical data: for long-time elites like yourself, the PDF will never tell the full story. Your suggestion to only import complete data and warn about older gaps makes a lot of sense.
I’m picking this up first thing tomorrow. Starting with a correction entry based on the PDF header totals so imported data can be automatically reconciled. The other improvements will follow right after that.
Thanks for taking the time to write this up. Exactly the kind of feedback that makes this tool better