Booker25 GoMeddo can handle conflict checking in two different ways.
Shared: Consider all dimension fields/junctions inside a dimension as a single dimension (Default)
Unshared: Consider every dimension field/junctions as separate for conflict checking
You can switch between the behaviors using the Use Shared Conflict Checking checkbox on the Dimension object. The default mode is shared conflict checking, which is recommended for almost all use cases. You should only consider unshared conflict checking if you have a specific use case that requires it.
Practical example
A clean Booker25 GoMeddo installation will contain a Contact dimension with a dimension field B25__Contact__c and a dimension junction B25__ReservationContact__c. The two distinguish themselves by having two different contact relations to the reservation. For example, you are using this system to create reservations with a primary contact from a customer (dimension field) and a list of guests (dimension junction).
...