Capture/Use click events on list items

Anton-du-Plessis

New [very] user, nd as all before me, very impressed by this platform. Been playing around and managed to get a few things working quite easily (with doc help, of course). But, I have been trying to get a form working and it does not want to play along.

In essence, I have one relation on the form with 2 lists. The first list has records related directly to the record being edited/shown, and the list records can be edited/added/deleted all ok.

The second list is related to records in the first list, and I would like to be able to click on list1 record, and then only show related records in the second list. There is an after change function on the first list, but it does not fire when clicking on the 1st list items (checked with console.log), but fires on open. Also, when it does fire, the app.get_field_value({F11: ...) returns an array with all the ids, not the selected/first/last.

I hope it is explained well enough, but in essence, can not find a way to get the 'clicked' row in the first list; was hoping to catch the 'event' somehow to get the selected id.

Form lists looks like this:

gabriel

Hello and welcome to the forum 🙂

To make it easier to discuss, what you are showing here as your "first list" is a relationship input - lists are their own thing and they work very differently to inputs.

But to your question:
There is no trigger point for functions available for inputs, except when they change their values, as you have noticed. Clicking on a record in a relationship input can therefore not be used to affect anything.

It´s strange to try to "click on" a record in an input field to filter another input. What happens after you save and then reopen the form? Does the filter still apply? Should the second input remove all invalid values, because the filter is gone after a reload?

Usually in your scenario, you would filter values from one input with values from another - that does not require function calls or anything like that, just a regular field filter.

I suspect that there is a misunderstanding. Maybe you could go into detail about your relations and what you are trying to filter?

Anton-du-Plessis

Thanks Gabriel for the very quick response, it is remarkable..

My ERD looks like this:

On the form, I show/edit publish_group and the blue arrow represent list 1 on my form and the related records are maintained in this list (add/update/delete)

On the second list, I want to show only the records related to a selected/current record from list 1.

I tried in second list to maintain the relation via the long route (green) but I think because the center object (publish_source) is repeated on the screen, it messes something up (after update, the direct relationship source -> connection is reset, related column is set to NULL)

On the form, I have the 2 lists:

And on F11, I set the after change JS, but that does not fire after updates to that list, only on save/open, and then the app.get... returns all IDs in the list, not just the added/updated one. F11 = list1 (blue), F13 = list2 (green)

F13 filter is set to filter via long route (green) using record ID of the _group, and ideally, _source should be added as only selected/current from F11, which is the part I just can not get.

I hope this is detailed enough to show what try to do. The reason for wanting the second list to show related only is to give complete picture on one form, without opening another to show only the related records. Quick way to just click on list one to see related in list 2, without going into edit mode. (less chance of someone changing things)

gabriel

Anton-du-Plessis

Unfortunately your ERD is unclear to me. Could you please advice, what your relations and relationship attributes are. Currently I would have to guess, but I am very unsure:

publish_group
publish_source is a n:m relation to connect publish_group to connection?
- ge_group_id is n:1 to publish_group?
- ge_source is n:1 to connection?
publish_target: Why is this connected to publish_source? Wouldn´t it need to be connected to publish_group? (each group having 1 source & 1 target).
connection: I assume this is the generic entity, that both source & target refer to (eg. which connection source/target use).

I have no clue, what publish_target is doing in this context. Please provide all relationship attributes and a short description, what the relationships between your entities are so that I have a chance to understand what you are trying to do.

Anton-du-Plessis

In principle, the ERD represents the following:

publish_source is an object, mostly a file, but could also be a table. This comes from somewhere, and can only come from one place - represented by the link to connection. (attribute ge_source -> connection)

This source object can be sent to multiple destinations, this is represented by the n:n relation between publish_source and connection, via publish_target. (publish_source <- publish_target -> connection)

publish_group is just a way to group the source objects, this represents an originating system/application and is just a way to partition the many source objects.

The current UI start with list of the groups, and on open opens up form to configure the sources (list 1) and currently shows all targets (list 2). But ideally, should show only the targets for a selected file in list 1. This is the part I am trying to accomplish. Showing the full target list is not helpful. If list 1 is big-ish and many go to same destination, then list 2 is just confusing. I added a link back to the source to show how they connect, but I think it messes up the form because as soon as the form opens up, it immediately shows that something changed (Save button enables) and on save publish_source gets updated and ge_source is set to NULL.

Thanks again for you attention, it is appreciated (from far away : )

gabriel

Thank you for your explanation. So if publish_source is your base entity and publish_group is for grouping sources, I would suggest you split up your forms as such:

You keep your list of groups. When clicking on a group, you open a form with a single publish_group as you already do.
On your publish_group form, you show a list of all publish_source related to that publish_group. When clicking on a source, you open a form with a single publish_source.
On the new publish_source form you can filter/edit publish_targets for this source as well as which publish_group this source belongs to. You can also set the form open option to automatically apply the parent publish_group record as default for new publish_sources, when creating up a new record from a publish_group.

This would cleanly separate, what entity you are editing on the different forms and would enable your relationship inputs to work as intended.

Anton-du-Plessis

Yes, that is what I realised / thought would be the way to go. It would be nice though to see it all on one form and filter by click event capture. Maybe in a next version 🙂

Thanks again for your very quick responses, it is excellent.