This topic about polymorphic relations is related: Polymorphic relations
The author has the following workaround:
in the Action column:
add a View for each type of polymorphic collection, then changing the linkage rules on those view actions to only be visible if the Booking type (collection select) matches what the drawer/dialog/page is designed for.
A Details/Form view of the specific relation in the popup/drawer/page then has to have its data scope set to show the relevant record(s).
However, this solution is costly and not particularly elegant.
It would be a nice feature to have a build-in functionality so that a click on a polymorphic class opens the corresponding inherited class.