How to list Linked Pages and Backlinked Pages in one page field?

[Yuri_BC]

Linked Pages is one relationship, Backlinked pages is then automatically created by Fibery.
The result is that both fields appear in the Page entity display.
How can I simplify that by showing Linked Pages and Backlinked pages in one page field?

[Yuri_BC]

Related:

Combine multiple relation fields in a formula

I have a database that is connected to multiple databases using relation fields, and I’m trying to use a formula field to combine all the content of the different relation fields. IS it possible to do it with formulas?

Related:

How to union two list fields in the same Database?

I have two list fields in my Database: Tags and [Project Tags]. (Tags is an x:many relation and [Project Tags] is a lookup of an x:many field.) I want to combine them into a single list field [All Tags], so if (eg) Tags = (foo, bar) and [Project Tags] = (baz, bam) then [All Tags] = (foo, bar, baz, bam). Is this possible? I can’t figure out how to do it with a formula or a lookup. Extra complication: ultimately I actually want the unique set of all tags, so if (eg) Tags = (foo, bar) and [Pro…

Related:

Relationship properties

This might be a big ask, but would it be possible to add properties to relationships as well as entities (like is possible with a graph database)? I realise that the more sophisticated you make the underlying platform, the greater the risk of users being scared away by the complexity, but for me, it would put you into a whole different league. It could be a feature that can be enabled but is disabled by default so as to not scare non-techies…

[Yuri_BC]

Use case: I have a database ‘Index’ which forms the structural framework of my spaces. It has the following relations:

Vertical Relations

• Parent Index: Self-relation many-to-one
• Sub Indexes: Self-relation one-to-many

Horizontal Relations

• Linked Indexes: Self-relation Many-to-many
• Backlinked Indexes: Self-relation Many-to-many

We don’t need the horizontal indexes to be specified whether they are outgoing or incoming, so having separate fields is confusing for users.