With rollup feature, how do I set up custom filtering by comparing values across 2 database tables

With Softr’s native database, is it possible to perform a “roll-up” operation with a custom filtering condition that compares two different fields across two different tables?

In Softr’s native database, rollup filter conditions reference fields and groups of fields in the same table.

I wish they could be crossing tables. It makes sense to do so, as the secondary table fields are being rolled up, the fields from the primary table are also available.

Do you have an example of what you would like to achieve?

Here is an example:

  1. Table A being production record, with records of each roll of fabric rolling off the production line. The fields include the finished product prodution process (e.g. needle punching, heat setting, glazing, etc.), and let’s call it “Process”, and fabric thickness. For a roll, the record look like:
    ”2511-CONEX140AM-89” “glazing” fabric thickness
  2. Table B being the inspection records. As the production is being manufactured, we record its thickness multiple times along its manufacturing process (e.g, needle punching, heat setting, glazing, etc.). Even for a particular process, we inspect multiple times. For example, the record would look like this:
    ”heating setting” “2.3”
    ”heating setting” “1.9”
    ”heating setting” “2.1”
    ”glazing” “1.8”
    ”glazing” “1.7”
  3. in Table A, for the thickness field, I want to rollup (average) the thickness fields in Table B, where TableB.Process = TableA.Process.

Because TableA.Process is a variable, currently I have no way of doing this.

Have you tried to add fields to Table A for storing the aggregated results (such as average thickness per process) and keeping these fields updated using Softr automations or AI Agents? Or would this result in too many fields?

yeah, I can do as what you suggested. But like what you said, there would be too many fields in Table A, as there are altogether 18 processes, but in reality I need only one field.

Tricky. Maybe someone else has a solution, but for now I can’t think of an easy one. Hope you find a way through this challenge!