<\/strong>This could be used where you have multiple cases related to a single requirement and you would rather track them under one Case than individually. In this scenario you would set up a Parent Case and all related Cases as Child cases of the Parent.<\/p>\n Scenario<\/strong><\/span>:<\/p>\n Consider, you have an incident recorded for fixing “Computer issues”. In order to fulfill this case we need to have in place the Hardware and the Software. Now, the Hardware and the Software are handled by two different departments in your organization.<\/p>\n So, to track the case ” Computer issues” we need to create two other cases one for Hardware Department and one for Software Department. As and when the other two teams finishes their work, our Computer issues case will be resolved too.<\/p>\n In order to make the tracking easier for such situations, CRM 2013 Spring ’14 update brought in a new feature called Parent Child Case.<\/p>\n Now, we can have ” Computer issues” as a parent case. And, Hardware Requirement and Software Requirement as two child cases.<\/p>\n Steps to make existing case a child case<\/strong><\/span>:<\/p>\n 1. On the cases home page select the cases for which you want to have Parent-Child Relation.<\/p>\n 2. Click the Associate Child Cases button.<\/p>\n Note: The only way to change the Parent Case of a Child case is by changing the Parent Case from the lookup on the Case Form.(Refer to the below image)<\/span><\/p>\n 3. Select the Parent Case out of the two selected cases and click Set at the right bottom.<\/p>\n 4. Open the Parent Case Form and you can see all the child cases associated with the Parent Case.<\/p>\n Steps to create a new child case<\/strong><\/span>:<\/p>\n 1. Open the case for which you need a child case. Click Create Child Case.<\/p>\n 2. You`ll get a Quick Create Form to fill in the details.<\/p>\n 3. Click Save and it`s done.<\/p>\n Note<\/strong><\/span>:<\/p>\n 1. Only 100 child cases can be associated\/created for each parent case. Relationship behavior<\/strong><\/span>:<\/p>\n Since there is a Parent-Child relationship between the cases, they should also support the traditional CRM behavior of being able to copy information over from Parent to the Child record.<\/p>\n Steps to Specify the attributes that will be inherited<\/strong><\/span>:<\/p>\n 1. Go to Settings -> Service Management.<\/p>\n 2. Select Parent and child case settings. 3. Select the Case attributes that will inherit from parent case to child case.<\/p>\n 4. Choose the closure behavior and then click OK.<\/p>\n Note<\/strong><\/span>: The above steps are not mandatory and may differ from situation to situation.<\/p>\n Whenever you set the attributes that will be inherited from Parent Case to Child Case using the above method then new mapping is created in the background for that attribute.<\/p>\n Example<\/strong><\/span>:<\/p>\n The attributes to be inherited are Contact, Case Title & Customer.<\/p>\n In the background following mappings take place:<\/p>\n The closure behavior explains the actions\/business logic to be applied when Cases as a part of the relationship are closed.<\/p>\n Merge Cases<\/strong><\/span>:<\/strong><\/p>\n Scenario<\/strong><\/span>:<\/p>\n In case of Parent-Child relationship, we did want to keep and track the child cases separately but still under a common cover that was the Parent Case. If on the other hand, if you would like to just track it as a single case and close all the other cases, you can now use the Merge Action. The Merge action is similar to the action that has always been available for Accounts and Contacts.<\/p>\n Steps to Merge Cases<\/strong><\/span>:<\/p>\n 1. Select the cases that you want to merge.<\/p>\n 2. Click the Merge Cases button at the top.<\/p>\n 3. Select the case that the other cases will be merged into.<\/p>\n 4. Now, hit the Merge button at the right bottom.<\/span><\/p>\n 5. Then, you`ll get a Merge Cases Prompt. Click Ok.<\/p>\n 6. The other case will be Canceled. And, only the main case will be Active.<\/p>\n 7. Now, when you open the Main Case record you`ll see all the merged cases under Merged Cases Sub Grid.<\/span><\/p>\n Note<\/strong><\/span>:<\/span><\/p>\n When you merge cases, other cases are canceled with status reason of \u201cMerged\u201d so they appear in Merged Cases SubGrid on the Case Form.<\/p>\n Conclusion<\/strong><\/span>:<\/p>\n Parent-Child Case is very useful in large organizations where there are multiple teams to take care of different tasks. With the use of Parent-Child Case it gets easy to track cases for which multiple teams are needed. Merge Cases feature is useful when there are multiple cases raised for the same issue and need to be handled by same person.<\/p>\n","protected":false},"excerpt":{"rendered":" Finally, the most awaited Spring \u201814\/SP1 update has been rolled out. It has brought along with it many new features and changes. The majority of the changes were observed in the Service Module. Here we talk about the 2 new features introduced in Cases: 1. Parent-Child Case 2. Merge Case Parent-Child Case: This could be\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[21,22,24],"tags":[395,990,1083,1296,1648],"class_list":["post-524","post","type-post","status-publish","format-standard","hentry","category-dynamics-crm-2013","category-dynamics-crm-2015","category-dynamics-crm-2016","tag-crm-2013-dynamics-crm-2013","tag-leo","tag-merge-case","tag-parent-child-case","tag-spring-release"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/524","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=524"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/524\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=524"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=524"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=524"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"img1\"](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/img1.jpg\")
<\/a><\/p>\n<\/a><\/span><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\n2. A parent case cannot be a child case of another case.<\/p>\n
\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/span><\/p>\n<\/a><\/span><\/p>\n