Opening form on grouped item

oriol

Hi,

I have a table with the following columns: asset_id, product_id, project_id. The rows all have the same project_id and are grouped by product_id. I want to click one of the rows (each has multiple assets) and open the form with any of the grouped assets as default, so i can get the common product_id and project_id and send it to a frontend function which affects the assets. I can't seem to understand how to do it, i've tried many combinations of grouping strategies, is there a "standard" way to do this or I have to find some workaround (saving a variable with an asset id, and getting it later, etc.)

Thanks!!

gabriel

I am sorry, but I do not understand how you´d have multiple assets per row. Do you use a sub query with aggregation on this? Or do you duplicate rows for each combination of project + asset + product?

A screenshot could be helpful, if that is possible.

In general, opening a form from a list, always gives you 1 record to open on that form. This can be from any joined relation on that list. This 1 record would then be loaded on the target form. But it sounds more like you want to create something new and use data from the list as defaults to be placed on the target form. This is unfortunately not possible with our current feature set.

oriol

gabriel So if I have 5 assets of the same product in the same project, with no groupbys or aggregations I would see something like this:

If i click on one of them, I get this

Which correctly calls a function that sets the consumed flag to as many distinct assets as necessary (so if out of 7 assets 3 are consumed and I consume 2 more I end up with 5 flagged as consumed)

However, if I group the assets like this:

By adding groupby to model, single record to description, and count to ID (which becomes quantity) when I click the project_relation and product_relation fields are empty.

Any ideas?

gabriel

Grouping kills the record ID association, so it´s useless if you want to access the individual records. Grouping is useful for overviews or totals, but not for editing.

What you can do is disable grouping and use sub queries instead. These can easily aggregate things as comma lists without needing to group.