Can we use Case reference data type inside embedded data type

I need guidance on how to design and implement the following scenario:

Scenario:

  • There is a parent business case called “PrimaryCase”.
  • Each PrimaryCase contains multiple “Item” records (for example,components).
  • For each Item, a separate and independent case called “SecondaryCase” is created.
  • These SecondaryCase instances are NOT child cases of PrimaryCase.
  • All SecondaryCase instances run in parallel and are considered sibling cases.

Requirement:

  • Display data from multiple SecondaryCase instances inside the PrimaryCase user interface using component as filter to fetch SecondaryCases
  • The data should appear as embedded data not as a child case view.

Is there a way to build EmbeddedData.CaseReference.Property1 and display in views?

Or what is the best solution to implement!

Expected Mockup is given below:

Primary Case

Header details:

Property 1

Property 2

Property 3

Component Details (Secondary Case)

Component Component Status Component Classification Component Substitue
123456 Active XYZ NA
456789 Active ASD 45645645-A

hi, yes definitely using combination of embed data ( your list of items) and data reference (DR property on item pointing to a case) is powerful pattern and often used.

I just found out a video showing how to use embed data and data reference. In this use case:

  • Approvers is the Embed Data field - it give me table with add/delete/edit options ootb
  • Cost Center is a Data Reference field on Approvers page lists - using this one gives me Search and Select

Combination of both allowed me to achieve following business requirement:

Allow users to select multiple case approves by search on related cost centers.

Thanks Kamil for the reply however I am not looking for Data reference inside embedded data, I am looking for Case Reference inside embedded data.

So as not to maintain other case data here as duplicate just link it and show in embedded data

Since its a case reference it will be a read only inside my embedded data

@RenukaD9 The procedure that Kamil shows is the same for case reference. Using a case reference field in your embedded data object would allow you to achieve the outcome shown in the video above. Below is the approach working for case reference:

Thanks Andreas for the reply I will try to implement and update here for everyone

It will work fine. You can think of Case Reference as subtype of Data Reference.

Hello Kamil! I am facing 2 problems with this implementation:

  1. I created an Report Definition and Data page. And I want to use a business property and not case ID as parameter for the data page, but when i save the property it gives error. “All class keys must be present in list of parameters”
  2. I want to add that case reference property in the embedded view. So if a Material is added in the row then that rows case reference field should populate the case ID.

Is this possible to implement?

regarding point 1, edit class definition and try adding this property as key on class.