Child Request is closed first then Parent Request is closed using Custom Entity. for e.g child request is updating of master details for parent request.
*This post is locked for comments
Child Request is closed first then Parent Request is closed using Custom Entity. for e.g child request is updating of master details for parent request.
*This post is locked for comments
I am not 100% clear on what you are trying to achieve, but just explaining a scenario.
If my understanding is correct, you want to prevent parent record from being closed/deactivated if there are any open/active child records.
If what you are looking is for the deactivate option, you will need to create a SetStateDynamicEntity message on the parent entity. In the Plugin message, you will need to retrieve all child records that have a state of active.
If the count of the results is > 0, that means you are unable to deactivate the parent, and you need to throw an exception that there are still open child records.
Was this your intention?
I have a scenario where their are 2 teams say e.g. Team A is handling Request - Parent which may have Child Request which is handled by Team B for e.g. Updating Master details of Main Request then unless Team B updates master details and closes Team A cannot close the ticket.
Hi,
Could you clarify what you want to do / what the problem is?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,280 Super User 2024 Season 2
Martin Dráb 230,214 Most Valuable Professional
nmaenpaa 101,156