Polymorphic relations. When creating relation, ability to have many Types from which to choose, and not just one Type

[B_Sp]

Wanted to chime in again as well. This is another pain point I would be able to really solve with Polymorphic. I have many Apps with a straight hierarchy “downward,” so if I could have just one Field to choose the result from that App, and not 3/4, it great simplifies my set up.

Likewise, I’d love to be able to see in a Collections field a list of relations from an App together, and not have to have several Collections for those.

Also wanted to point out support for @Chr1sG your commentary over at:

Fields applicable to all types

Yes indeed, and if it were possible to define fields that are to be available for all entities, then one could achieve a sort of polymorphism. Say I create a new type (called ‘LinkAll’) and then I define a field for all types (called ‘Poly’) which is a relationship to ‘LinkAll’. Suddenly, a ‘LinkAll’ entity is capable of being connected to any entity in the app/workspace. Of course, the basic implementation of this would result in the ‘LinkAll’ entity having a large number of fields (one for e…

…and I can’t help yet again remark how the app we are using here in the forum, Discourse, does a great job of bi-directional and contextual sharing/transclusion - example right there where I could just quote from that entire thread, not reference all of it.

Cheers guys!