You need to sign in to do that
Don't have an account?
Sudipta Deb
Multiple Active Entitlements Associated With Single Contact
Hi Folks,
I would like to understand one use case - "Is it a valid scenario to have multiple active entitlements associated with Single Contact/Single Account?
From the below document about "Automatically add entitlements to the case", I can see the code is written such a way that it may possible to have multiple active entitlements against a contact or account. In that case, trigger will link the first entitlements to the case and break the loop.
Also don't you think so that while considering entitlements for Accounts only(Cases without Contacts, but having Accounts), it should consider only those entitlements which are associated with Account, but not with Contacts. May be create a roll-up summary field in Entitlements with counts of EntitlementContacts. Query(To Fetch Active Entitlements for Accounts) will only consider those entitlements for which the roll-up summary field value is zero.
I would like to understand one use case - "Is it a valid scenario to have multiple active entitlements associated with Single Contact/Single Account?
From the below document about "Automatically add entitlements to the case", I can see the code is written such a way that it may possible to have multiple active entitlements against a contact or account. In that case, trigger will link the first entitlements to the case and break the loop.
Also don't you think so that while considering entitlements for Accounts only(Cases without Contacts, but having Accounts), it should consider only those entitlements which are associated with Account, but not with Contacts. May be create a roll-up summary field in Entitlements with counts of EntitlementContacts. Query(To Fetch Active Entitlements for Accounts) will only consider those entitlements for which the roll-up summary field value is zero.