As a user I want to easily import items related to a certain parent item, regardless of whether the entity reference field is in the structure of my imported data or the related data's structure.

For example:
From a Child's profile, I would like to click "Import School Enrollments for this Child" and then use the Import Module's "additional" in step 2 to pre-select the childId:

This is currently only available if the Child (not the imported School Enrollment) record hold the entity field, pointing to the imported records. In this example, the structure is the other way around.

(It is possible to import this reference in step 3 by mapping some column of the import data that holds a key to the child. But this requires more preparation from the user outside the system. And it is confusing for users why some linking can be done in step 2 and other only in step 3)

Very specifically as a test case:
The system should offer an Advanced Import Action when importing School Enrollment. This should let the user select one Child from the dropdown to which all records will be linked/prefilled.
(For this example, because School Enrollment entities also have a schoolId field, another Import Action would be available to do the same to linked to a fixed school, also)

Questions & Tasks:

• find all entity fields and offer them in step 2 to be filled with a fixed selected record
• what do we show in step 3 (column mappings) to avoid users overwriting the fixed value with a column mapping