Passing data from list into function/other components

Mrti

Hi all! I love the platform, I've been checking it out lately and there is only one missing piece I need to use it.
Is there any possibility to pass marked rows data from list into function?

I got 3 examples:
Example 1:
I have list of company departments. I'd like to execute some kind of action on certain number of departments, but not all of them. I've marked 6 out of 12 visible rows and now I want to click big green button "do something" and... it does something - only to the selected rows. (maybe function that takes array of ID's as an argument is my target)

Example 2:
I am browsing through the list and one particular record interested me. I'd like to execute action on it and only on it.
I checked the row and now I am simply clicking button on the top of the form and magic happens.

Is this possible with REI3? I've been looking through the documentation but I can't find anything that could help.
The only purpose of multiple selection in component "list" is only to do bulk editing and nothing else. I couldn't even find any way to do single selection - clicking simply opens form.

Example 3:
I'd like to choose single company on the list, and after choosing, list below (sublist) is filtered and shows all departments beloning to chosen company.

I looked through documentation and tried playing with various stuff in the builder but I couldn't get any of the examples to work.

gabriel

Hello Mrti and welcome to the forum 🙂

Unfortunately, the missing feature here, which we internally refer to custom list and/or column actions, is not implemented yet. It´s on our own wishlist but not prioritized at the moment.

You can however get pretty close with existing features for some of your use cases:

Example 1: Besides a regular form, you can also add a "bulk editing form" in the list field settings. This form is then used if you check one ore more records in the list and click on "Edit" in the list field. This bulk editing form is then opened with an array of IDs (all selected records). On the form itself you can place a button that executes your desired action - to get the IDs you would use the frontend function "get_record_id".
Example 2: Would work the same as example 1 - you would just handle one record ID instead of an array of IDs for your action.
Example 3: Here there are multiple ways to approach this. You can open the record on a new form to show sub entities (eg. departments of the opened company). The other option would be to use a relationship input field for the company (instead of a list) and then use the value of the input field as filter for another list showing departments.

Mrti

Thank you very much for the response.

Example 1 & 2.
The problem with it is that it takes real bulk editing out of a question I think... hmm unless I can put button for opening real bulk form in the "custom" one. I'm gonna try that.
// edit: I just tried that. It kinda works. I put 4 buttons on separate form that is being opened as a bulk form. Issue now is that I can't open real bulk form now, haha. 4th button is supposed to open "company_bulk_edit" and even when I set upt record ID it opens up in "new" mode.
// edit 2: tried with front function to open bulk form but unfortunately no luck. REI tries to cast array of integers into single integer -> unable to encode []interface {}{1, 2} into binary format for int4 (OID 23)

example 3.
Unfortunately it won't do for me. In my (humble) opinion ability to browse data very fast is crucial - by browsing fast I mean having an option to filter 5-6 views/lists simultaneously without opening 10 forms on the way.
Are there no other options...? Is it possible to create custom components maybe using javascript or something like that?

gabriel

Mrti

The same bulk editing form can be used for both regular bulk editing (by adding input fields), as well as bulk actions (by adding buttons or form actions). When you open multiple records in that bulk editing form you can either use the inputs and save changes to update these records - or use custom actions to execute things for the currently open records.

Regarding example 3: You can have multiple lists open at the same time, filtered differently based on inputs on the same form. The thing that currently is not possible, is to filter one list with the selection of another.

There is no option to add custom components to the frontend, unless you add them to the source: https://github.com/r3-team/r3

Martin

Example 3 can be somewhat done with a subform, no? It is a horizontal divide, not vertical, so it might or might not fit in your use case.

Example:

Mrti

Thank you for responses.

@gabriel
Editing source is not for me, I'd have to learn how to do that and then maintain my changes along with new versions.
This is my personal project, so it's not worth the work I would put into it (I need to manage my time carefully).

May I ask why is it not prioritized?
I would say, ability to run actions straight from list view is one of the most important things (for end users).
I've had users straight up refuse to do anything unless they could do that in my last job. Even better, people could not understand the context of what they are doing beacuse of additional windows. And of course, it's a matter of doing things fast and when users can see directly what they are invoking actions on (I dunno how to call it differently)

Martin
I would have to check it out, but I am somewhat suspecting it won't do it for me. Will try that out.

gabriel

I can only speak from my anectodal experience. But when someone says "X is the most important feature and needs to happen now", its hardly universal. We got requests 2-3 times regarding this feature - and we also want it for ourselves - but it´s far from the "the most important", at least from what I can see.

Right now, we have resources we need to spread between working on the platform and supporting paying customers. Because the vast majority do not pay for r3, we need to prioritize accordingly. If a customer wants feature Y instead of list row actions, feature Y will usually win out.

Of course this is not always the case and we build plenty of features into the platform because they are really awesome to have. But yeah, that is the dilemma in a nutshell. The feature will come, but I cannot promise it for any particular release.