Also for additional context I keep track of peoples hourly rate in the airtable database and when I change someones rate it’ll change all their past payouts, which is bad for accounting.
Also for additional context I keep track of peoples hourly rate in the airtable database and when I change someones rate it’ll change all their past payouts, which is bad for accounting.
Thanks for that additional context, Michael. The way that I solved this is to use a eRates]
table. Each line item links to a rate record. Each rate record has a starting and ending date, and I can only link to active rates (with only a start date). If a rate needs to change for a given client, I add an end date to that rate record, make a new rate record with the new rate and a starting date, and link all new entries for that client to the new rate record. None of my old data changes because older line items are still linked to the original rate record.
Thanks for that additional context, Michael. The way that I solved this is to use a [Rates]
table. Each line item links to a rate record. Each rate record has a starting and ending date, and I can only link to active rates (with only a start date). If a rate needs to change for a given client, I add an end date to that rate record, make a new rate record with the new rate and a starting date, and link all new entries for that client to the new rate record. None of my old data changes because older line items are still linked to the original rate record.
Ohh that’s smart… thanks Justin!