You need to sign in to do that
Don't have an account?
Patterns for implementing many-to-many relationships between SF Objects
I'm new to SF developement and have not been able to find a recommended 'best-practice' for representing many-to-many relationships between objects.
I've designed the following entities:
i) Invoice - Representing a demand for payment - which may be payed through multiple payments
ii) Payment - Representing an actual payment (which may be allocating 'across' multiple invoices.
iii) PaymentAllocation - Essentially a relationship container - associating a paymentId to an invoiceId
The later would be populated in Apex space and is my attempt to repersent this sort of many-to-many relationship which does not appear to come out of the box.
I was hoping that others would advise as to the recommended 'SalesForce' way of accomplishing this sort of relationship/behaviour?
I appreciate the feedback.
Thanks,
Raf