Duplicate transactions

[Niraj-Fonseka]

[ Current ] -

• A hash is generated for each transaction to make them uniquely identifiable. This was also used to make sure to not allow duplicate transactions to get created. But there are certain scenarios where sometimes same charge can get applied with the same fields for multiple different transactions
• Parking meter extensions
• Wending machine

[ Changes Needed ] -

• Need to figure out a better way to handle this

[Niraj-Fonseka]

we may have to deprecate generating a hash with the data. Instead we can add the functionality to check if the first record of the date that's getting ingested and see if that date comes after the start date.

[Niraj-Fonseka]

or we can handle this at the time of ingestion. Go through and add every duplicate record and still proceed with using the hash

[Niraj-Fonseka]

34 sub story of this