Regarding major incident management

[sriramsin]

Hello Everyone , 
I have created a flow to create a major incident when more than 5 incidents are created , then map those incidents as child to the major incident , but major incident it created , but the child incident is not mapping to the major incident. In the related list of the incident form , it is not showing the child incidents . Help me to solve it 
Thanks in advance .

[Rakesh_M]

Hello @sriramsin ,
please  share execution details screenshot

[Rakesh_M]

Hi @sriramsin ,
You cannot set a Major Incident as a child incident. This action is restricted by the business rule: "Child incident cannot be major incident."

Please update the lookup filter to exclude Major Incident records by adding the condition:
Major Incident State is None.

[amit_bt]

The most likely reason your child incidents are not appearing in the related list is that you are populating the wrong field. To fix this, you must ensure the parent_incident field is populated on the child records, not the generic parent field.
>>>Identify the Correct Field: On the Incident table, the relationship for the "Child Incidents" related list is built on the parent_incident field.
>>>Update the Action: In your flow, after the step that creates the Major Incident:
>Add a "Look up Records" action to find the 5+ incidents that need to be linked.
>Add a "For Each" loop to iterate through these incidents.
>Inside the loop, use an "Update Record" action.
>In the Fields section, select Parent Incident (backend name: parent_incident).
>Map this field to the Data Pill of the newly created Major Incident record.
>>>Check the Related List Configuration: If the field is correctly populated but still not visible, verify your form configuration:
>Navigate to the Major Incident record.
>Right-click the header and go to Configure > Related Lists.
>Ensure that Incident > Parent Incident is in the "Selected" slushbucket