I have page list in child case which is referred to savable data page(Source data is retrieved from parent case workpage by passing coverinskey), when i update any record in the child list same should be updated in the parent case.
Use a data reference field in the child case, select some items, then just use an update case step in the flow to propagate the data from child to parent.
Yeah that is one way, but can i update using savabale data page? since i m using the same savable data page to refer the list when i do changes in the list, will savable datapage takecare of updating the case in parent
@yt110154 please check out this, I cover the end to end for doing it Can anyone help me to fix this issue? I'm new to pega and seeing this error for the first time - #15 by MarcCheong
As for parent case, so long as it has a data reference to the list you just saved it will be fine. IF you need to invalidate that datapage (so it loads again) you can use How to notify users to refresh an outdated List View in Constellation UI
i see that if savable dp structure is list i cant use dp in data reference type property
Data reference means, that data page is used to show the options and you need to select the data from those options. But, what is there to save here? The items you select in that data reference field are stored in the case type. Your objective is to copy the selected items from child case to parent case. That may not be possible with the savable data page approach.
@yt110154 could we go back to the business outcome? What is the scenario trying to be achieved.
It sounds like the parent and child are both looking at a list of items? Let’s say addresses, when I update my billing address in the child, we want to make sure that the parent see’s the new billing address?
In this case, a saveable datapage would work OR a list view on the “address” data object with CRUD enabled. See Configuring Actions for data objects or Managing external system of record through REST with CRUD actions in Pega Constellation.
An “on bulk” change of data objects, where all are editable is not possible with saveable datapages, even in the UI this is not possible (until '26). I would suggest using embedded data in child and/or parent, then individually saving those back to the data object. You’d have to take care to show the data reference when in read only and copy the data reference to embedded when you want to edit.
Scenario: I have a embedded list in parent which have set of items. i need to show the same items in the child, i dont want to propagate entire list instead i want to have one datapage which i can refer to one list property in child. Why datapage? what ever the chnages i do in child list property should be dynamically change in the parent list (since i m using datapage as refer i expect to modify parent list). Similarly what ever the changes i did in parent should reflect in child.
for the above use case i have a savable datapage, which refered to query type peroperty (which not allowing me to edit). If it allowed me to edit what ever changes i did should refelct in parent case bcs its savable.
Data model “theory”
My gut instinct is should be a data reference for both the parent and child.
Why? Because data reference is used for data that lives outside the case. embedded is for data that lives purely in a case.
The fact you have data “shared” between cases, suggests it lives outside the case.
Parent / Child
Only further supports this position. You do not want an update to the list in the child being blocked from updating the parent because someone else has updated the list or has the lock on the parent.
This list should live outside the case?
In practice
Authoring a data model, does not allow you to select list pages
I suspect this is reverting to “query” because you’ve changed this in Dev Studio, this kind of invalid combination commonly changes a data reference to query.
Data Reference - Multiple = Picker
Unfortunately, even if I “do this right”, and place the saveable list page in the view, Constellation is assuming this is an ordinary data reference - multiple records. It gives you a table or combo-box to select records.
My Conclusion: Saveable data page - multiple records is not the right way to go
Solution: List views
Happy to be proven wrong here, maybe I’m missing something, but I would really make this a List View / Insights, and store the data as its own object and you list views/crud to update them.
This is configured:
-
As a list view on my case
-
Allow CRUD
-
Then placed in the view of the action (configure view)
-
Run time allows you to view, edit, delete etc. AND would be the same on both parent/child
Configured in 25.1.2 
Thanks for the details, We have achieved the above mentioned scenario by using Case Reference property type (by accessing the required page list through Look up datapage)
Genius! i didn’t think of that, a nice way yo reference something belonging to another case!