Hi everyone!
I am working on implementing the relationship system to replace the currently used external enumerations.
In our use case we have 3 important instances.
- Bookings 2. Partner 3. Account
A booking can reference one partner and one account belonging to said partner.
A partner can be referenced by multiple bookings and it can own multiple accounts.
An account can be owned by a partner.
In a booking we want to select the partner and the account. (See the picture below)
Right now, we have a relationship between Booking-Partner and Partner-Account.
My questions is whether or not we have to introduce a third relationship : Booking-Account or if is sufficient to keep it at two relationship models.
Will those different solutions have different impacts on the project?
Thanks in advance!
Best regards, Kilian
Hi Kilian,
thanks for your question and sorry for my late response.
So far, it is only possible to create a direct relationship between two entities. If it is required that a Booking is also linked to an Account, you need to setup a third relationship.
The advantage is, that you can set/edit all necessary links inside one document (if modelled correctly), i.e. having the Booking document displayed, you can set both, Partner and Account. Of course, this is also possible from inside the Partner or Account document.
However, the downside is, that all available Accounts (from various Partners) and all available Partners (from various Accounts) will be displayed for selection since all three relationships exist independent of each other. In your particular case, the user needs to be extra careful when linking entities to avoid mistakes. If not, you might end up with the following inconsistent situation:
Booking1 is linked to Partner1 and Account1, but Account1 is linked to Partner2 (not to Partner1).
Best
Thank you very much for your answer! This helps a lot.