MMEX Discussion Forum

I noticed the last transaction for my accounts have a very (very) large number for the ID, I don't think this is normal?

[media]https://ibb.co/5WPdPW9B [/media]

I downgraded my DB file to the backup copy from 2/5 and downgraded to MMEX 1.8 (from 1.9) and now transaction IDs are working properly. Something broke between 1.8 and 1.9 with the ID being astronomically large in 1.9.

Do you try to look for an answer in this forum ?
Because the answer is already blowing in this forum.

And transaction IDs work properly, from the 1.9.0
Everything has an explanation

There are at least three other posts discussing this topic. What you are seeing is not a bug, but rather a new feature introduced in MMEX 1.9 called SUID (Sequential Unique Identifier).
see there:
viewtopic.php?t=11317
viewtopic.php?t=11258
viewtopic.php?t=11321

This change ensures that each transaction gets a globally unique ID, which helps with database integrity and syncing across devices. While the numbers may seem unusually large, this is completely normal and does not affect functionality.

If you prefer the old behavior, downgrading to MMEX 1.8 will revert to the previous ID system. However, using MMEX 1.9+ with SUID is recommended for future compatibility.

That's my bad, I do see the other posts...maybe a sticky is in order or a call out of some sort to this new "feature", it's very odd to go from 2000 to 17 quadtrillion for the ID #. What exactly was wrong with the old system? Literally for 16 years (I started using MMEX in 2009) it's worked it's way from 0 to 2176.

OK....I see why they did this: https://github.com/moneymanagerex/money ... ssues/7174, it's to fix a duplicate id issue during an import.