What happens to the old invoices when a rate, say Senior Dev, increases in the future ? I am not sure if we could have, in the juncton table, a column with dates, just to allow keeping only one rate with a 'applied from..to..' column and filtrering with the date of invoice. Would it work ?
Instead of a junction table, couldn’t you just add additional role levels? This way your primary key is still Name | Role. Also, what if Debbie increases her rate but her title doesn’t change? lol
Yeah, for this example that totally works, too. But I prefer to have one record for the team member. This way, you don't have duplicative data, like their phone number, address, etc. Especially if you build automation from your staff table for onboarding or other workflows
Grab our automation training 👉👉 gapconsulting.io/webinar-registration 🤓🤓
Start a free trial in SmartSuite 👉👉 partners.smartsuite.com/8ust3byf6ihl ✨✨
Thank you so much Gareth! You remined me the same use case in Airtable (that was excellent video)!
What happens to the old invoices when a rate, say Senior Dev, increases in the future ? I am not sure if we could have, in the juncton table, a column with dates, just to allow keeping only one rate with a 'applied from..to..' column and filtrering with the date of invoice. Would it work ?
A smart suite video on a Monday? The heck
Instead of a junction table, couldn’t you just add additional role levels? This way your primary key is still Name | Role.
Also, what if Debbie increases her rate but her title doesn’t change? lol
Yeah, for this example that totally works, too. But I prefer to have one record for the team member. This way, you don't have duplicative data, like their phone number, address, etc. Especially if you build automation from your staff table for onboarding or other workflows