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, i…

Actually, I have a completely different use case but similar approach as @Chr1sG is asking for. If you’re taking a value engineering type approach to product development, you may want to refer to certain measures/scales from a feature request (benefit hypothesis). For example: Due to <insert ins…

That’s an interesting example, thank you! Have you settled on this approach in your company? I’ve seen folks describing models like this one, but I haven’t seen one in use yet. Would love to hear about your first-hand experience.

Hi @antoniokov - not settled, but we’re defining our target framework at the moment. I mean, one way one could get around it would be by defining these MEASURES fields per app or per entity. But even so, you would be missing the ability to define GOAL and RESULT (after, say a product/feature exper…

Just wanted to bump this one. There are just so many use cases where a relationship property would allow very rich information without overcomplicating the model. e.g. How much is a Product/Solution Capability dependent on Component A? e.g. Teams Skill mapping: To what degreed does a require (an…

As a social systems developer, I am a huge fan of relationship properties, since they reveal the meaning in relationships, and much more information is available to work with in analytics. I have tried to workaround this in Fibery using an entity type with endpoints A and B and automation buttons, …

I am wondering if it is possible to extend the relations fields to capture some attributes related to the relation. This is inspired by the highlights feature which allow you to not just link two entities together, but add some fields/attributes to add context to the highlight as well. If we were ab…

[image] cannibalflea: I assume that many-to-many relations are already have a junction table which could possibly be extended. Actually, that’s not how they work, but never mind! I suggest checking this topic out and if you think your need is covered, vote for it and I will merge them.

Ha, I cannot believe I hadn’t seen this topic yet. I would love to have this. For our product architecture on Fibery I can use this in the data modelling but also when connecting API calls with data, events and so forth. Would love to be able to give relations the full plethora of fields (e.g. sin…

@Chr1sG I should have searched a bit harder. I had actually commented on that thread and voted for it :sweat_smile: I’m getting to the end of my ideas and just recycling. Happy to delete this post or merge it. I didn’t see any details from the fibery team on the technical constraints of this and ho…

Relationship properties

Ideas & Features

Yuri_BC December 21, 2023, 11:57am 15

Related, although that development focuses on in-text references, some architecture may be useful for potential Relations as entities (Relations Reloaded ;-)):

Topic		Replies	Views
🦜 April 2, 2026 / Show Fields from relation without Lookup, AI Integration Agent Changelog	47	834	June 3, 2026
CHANGELOG: October 1 / Create Documents and Whiteboards inside entities, Automatically link entities based on rules Changelog	31	4666	March 28, 2021
Representing nested relations Ideas & Features	31	3835	February 12, 2026
Fields applicable to all types Ideas & Features flexible-domain	13	3523	September 7, 2020
[APPROVED] Polymorphic relations. When creating relation, ability to have many Types from which to choose, and not just one Type Ideas & Features flexible-domain	75	9337	September 15, 2026

Relationship properties

Related topics