Though I am a little unclear on the specifics, what you would do to filter data in the rollup is to create new columns with the filter parameters, like start, and end date, and a checkbox, then formulaically reference those columns inside of the rollup (with an if statement or another formula). Then in the interface you can create fields for the columns you created, and the value in the rollup field would change depending on user input
Though I am a little unclear on the specifics, what you would do to filter data in the rollup is to create new columns with the filter parameters, like start, and end date, and a checkbox, then formulaically reference those columns inside of the rollup (with an if statement or another formula). Then in the interface you can create fields for the columns you created, and the value in the rollup field would change depending on user input
Thanks for the answer but that doesn't solve the issue, as what I'm trying to do is make the filtering dynamic.
The interface already has a Filter element, and by using 2 levels in the list, I'm able to show only the appropiate records. However, the Rollup total does not update accordingly, and continues to show the total Rollup.
Perhaps an image will help:

As you can see in the image, the Filter works for showing only the desired Services associated to a Dealership, but the Amount (which is a Rollup) is not updating accordingly. It is still showing the sum of all of the services associated.
I have the exact same problem so I am following this post.
What you would need to do is create a custom filter and not use the filter component. You would have a separate “Service Date” field where your user inputs his filter parameters and display it as a single text or date field in the interface. Then you would set conditions in your roll up based on the inputs in this field.
in order to have user specific options you would have a user table and have the service date field live in there then use a look up to bring it to the other table. In the interface you would create a record picker of the user, then connect other components to it, making them unique to the user