I have a customer who would like to relate customer complaints against subscriptions. Currently it is possble to have a 1 to 1 relationship between a subscription and a communicationEvent, but not a 1 to n relationship.
Anybody any objections to add the CommunicationEventSubscription entity similar to the CommunicationEventProduct entity? if this is ok, shouldn't we remove the communicationEventid field from the subscription entity? please let me know your opinions. -- Regards, Hans Bakker ANT Websystems Co.,Ltd (http://www.antwebsystems.com) If you want to verify that this message really originates from from the above person, download the public key from: http://www.antwebsystems.com/hbakkerAntwebsystems.asc
