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 ![]()





