No compound actions on Relation buttons?

I am surprised there are no compound actions on a relation button. Is this something in the roadmap?

3 Likes

What do you mean with ā€œRelation buttonā€?

Possibly Manan means a list relation component.

1 Like

I never even knew this ā€œButtonā€ existed before I saw this post, and I canā€™t find any reference to it in the docs. I just tried it, and it seems to be a button in name onlyā€¦

Seems to be that the difference between this and a List Relation is that it can only use a relation as a source, whereas a List Relation can use a Sheet or a Relation as a source.

Seems a bit redundant?

Curiosity got the better of me :joy:
This helps to visualise the difference between the 3 relation options. All three here are using the same relation as a source, with default settings:

4 Likes

I use the ā€œrelation buttonā€ for single relations ā€” like a link to the userā€™s profile for example.

List Relation is my least used relation-related item, mostly because you canā€™t customize the word ā€œItemsā€ and if there is only one item attached to the list, it loads that single item right away and changes the way youā€™d expect this list relation to work. I think thereā€™s room for improvement in both the relation button and list relation components. I think theyā€™ve been put on the back burner as other things were made awesome haha

6 Likes

If I donā€™t need single Lookups, I always use a multiple relation with an inline list. Especially when a single row is found. There is so much more customization available for an inline list. I can see some rare cases for using a List Relation, but I see no reason whatsoever to use a Relation component when an Inline List can do the same thing with more customization.

And to follow up on @Manan_Mehtaā€™s question. If Iā€™m understanding the same as the others, I donā€™t think of the Relation component as a button. More of a single item list. Just like how a List Relation changes itā€™s view between showing the details when there is only a single item vs showing the number of multiple items in a list. I think both the List Relation and Relation components are quite old and donā€™t get a lot of updates.

3 Likes

Oh got it. I use it only sometimes, a little. I prefer using inline lists with filter or with relationsā€¦
But thatā€™s a good question

1 Like

I use this button when I need something which cannout work with a ā€œmultiple relationā€ (Set columns majorly)

The way an inline list has an option to set up compound actions, I think the relation button also should have the same option.

In my use case I cannot use a multiple relation because of various reasons.

3 Likes

Would you be able to use a multiple relation for displaying the inline list along with a single relation for the the set columns action?

1 Like

The last app Iā€™m using it, btw itā€™s an app I submitted to templates and Iā€™m waiting approval

Simple way to do a ā€˜profile button/linkā€™

4 Likes

I donā€™t think I ever use single relations anymore. For displaying purposes, I use an inline list. If I want to take a specific value out of the relation, I use a single value column.

3 Likes

What I am trying to achieve is this:

I want to view details of that particular relation and I want to set columns in that row using the value from the screen I am navigating from.

The problem:

  1. Using a normal button, I have no option of ā€œview detailsā€
  2. Using an inline list, I have no option of set columns using values from the screen I am navigating from (While this is available in a normal button if my relation is a single relation)

I thought this could have worked perfectly with a relation component which has the 2 actions I mentioned.

4 Likes

Ditto. The ā€œrelation buttonā€ cant have actionsā€¦inline lists can. So I typically do a multiple relation even if itā€™s a single relation that Iā€™m looking for just so I can use the inline list component.

2 Likes

Well maybe that means the single relation could have better design options along with Actions which would make it powerful and usable.
And we wonā€™t need to check the box for multiple relations when we donā€™t need multiple. (Because lot of other functionality gets affected by that checkbox)

1 Like

Completely agree. Several of the components could benefit from enhancements (title component, relation component, image component, etc).

3 Likes

+1