Would it be bad form to: 1)extend the PaymentMethod entity so that the PK includes the paymentMethodId and the partyId?
AND 2)not allow duplicate PaymentAccount Number entries(in an entity similar to the EFT Account)? With the OOTB PaymentAccounts, a user/multiple users can have multiple instances of the same CC or EFT Account Numbers. For my application I am thinking this might cause some validation issues downline for us. Basically, I would have only 1 instance of a PaymentAccount number that belongs to a party(Principal_Investigator). Users can use this account which is why I would need the additional PK field on the paymentMethod entity. I think I would need to remove the PaymentAccount update/edit feature. Perhaps my lack of db design experience was just revealed. Can you think of any problems the above may cause? -- View this message in context: http://www.nabble.com/Extending-the-PaymentMethod-entity-and-restricting-PaymentAccount-entity-tp22264024p22264024.html Sent from the OFBiz - User mailing list archive at Nabble.com.
