Would be great if the transaction IDs were consistent on the exports. When I run two exports for overlapping date periods, the same transactions have different transaction IDs. This defeats the point of assigning them a unique code, and makes it impossible to use features like vlookup when you’re dashboarding or further analysing your spend, post-export.
Hi @esdellert,
thanks for sharing this!
Transactions change all the time, so this is insanely difficult; I’m going to pass it to the product team, but as I mentioned we are ware of it. ![]()