how we can attach change to problem related list in sow as well as native view

[RamuN]

Hi Team

i have created below record in sys_m2m table in global application

and then  added change request as shown below in sow view 

in native UI it is working as expected when we create change using New ui action from problem related list is attaching to problem related list when we create change and vice versa

but when i am creating change from service operations workspace view using ui action the change is not attaching as well as it is redirecting to differnt table (M2M (u_m2m_problem_change_request))

Please suggest

[Dr Atul G- LNG]

Hi @RamuN 

Apologies, due to an issue in the community, the images are not visible. Could you please attach the images instead of copying and pasting them? Also, I'm not sure why a new table is being created — you can simply add a change on the Problem (PRB) OOTB related list.

[RamuN]

Hi @Dr Atul G- LNG 

Thanks for the response

when we try to attach the change on the Problem (PRB) OOTB related list

the issue is problem is not visible under  change (CHG) OOTB related list OOTB

please find updated images

[Dr Atul G- LNG]

Hi @RamuN 

Greetings!!

As per OOTB (Out-of-the-Box) behavior, if you add a Change record to a Problem via the related list, you will see the associated Changes listed under the related list in the Problem record — like this.

However, when you open the Change record, it won’t show the Problem under the related list, because this is not a many-to-many (M2M) relationship. Instead, it's a parent-child relationship. So, as per OOTB design, you can see the linked Problem in the Parent field on the Change record — like this.

[Gaurav Shirsat]

Hello @RamuN 

Use Case 1: for Native UI

Please Find way to create This Manually :

Add Related List in Native View (Classic UI)

Steps:
Navigate to a Problem record (problem table).

Click the gear icon (Personalize icon) > Configure > Related Lists.

In the left list (Available Related Lists), search for Change Requests [change_request].

Use Case 2:

1. Go to UI Builder:

             Navigate to: Now Experience Framework > UI Builder

    2. Select the Experience (e.g., Service Operations Workspace).

    3 .Choose the Record Page for the problem table.

    4.Find or add a Related List component:

    5.Add a new "Tabbed Form" or scroll to the Related Lists section.

         In the configuration of the related list section:

    6. Choose the change_request table.

         Set the relationship (ensure it's filtering records where problem field = current problem record).

     7. Publish the page.

I saw you have already replied that it isn't working:

Please debug and check that : 

• The relationship exists in the data model.
• ACLs permit access to the change_request data.
• The problem field exists in the change_request table.
• Optional: Create a Relationship Manually (if needed)

If the relationship doesn’t exist (e.g., the change_request table doesn’t have a problem field):

Steps:

If your instance has a customized relationship model (for example, using task_rel_type):

1. Go to the Task Relationships table:

   • Type task_rel in the Application Navigator, then open Task Relationships.

2. Click New.

3. Fill in the fields:

   • Parent Task = Problem Ticket

   • Child Task = Change Request

   • Type = (Choose the appropriate relationship like "Caused by", "Related to", etc.)

4. Click Submit.

Thanks and Regards

Gaurav Shirsat