Do I need a Many to Many relationship?
My company is having an integration developed between our Booking Software and Quickbase to aggregate our bookings from all of our stores in one place. The data that is associated with this booking is...
Forum Discussion
The relationships that you will need are as follows:
Customers -> (has many) Bookings
Customers -> Transactions
Bookings -> Transactions
The person writing the Integration should push all the data to the Bookings table and then have either webhooks or other custom code to associate the booking with a customer (or create a new customer).
The kicker on this is to identify a unique identifier for the 'customer'. Which is most likely the email address.
Honestly if you have somebody writing the integration, they should know this. If they don't, I'd be weary of their code as well.
Customers -> (has many) Bookings
Customers -> Transactions
Bookings -> Transactions
The person writing the Integration should push all the data to the Bookings table and then have either webhooks or other custom code to associate the booking with a customer (or create a new customer).
The kicker on this is to identify a unique identifier for the 'customer'. Which is most likely the email address.
Honestly if you have somebody writing the integration, they should know this. If they don't, I'd be weary of their code as well.