- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi @kapilKochar
If you look at the Target Mapping configuration you will see a series of field you can set to manage the standrd exclusion it is done via DenyList
In your B data schema, you must allow to capture these fields and of course you need to have a field to capture the email address. For ease, you could name these fields same as in nms:recipient
The new entity has its own Delivery, Exclusion, and Tracking Logs schema as expected.
DESIGN CAUTION:
1- Avoid to have a composite fields as a PK, although it does work, for very large table, this is definitively not the most performant design. Use a single field for your PK
2- Since a single PK field is strongly advised, please name it simply "id", otherwise, the billing workflow might fail. It did in the past, so better to play safe. ideally you will use autopk AND a custom sequence, do not use the standard xtkNew as a sequence if you decide to go with autoPk... You will get into trouble once the sequence expires...
As for the subscription, it is true that Subscription (nms:subscription) is very much tight up to Recipient () and you will have to replicate it for your new B schema and using pre-defined filters you should be able to provide similar features...
Hope this helps,
Thanks
Denis