Hi @eve,
I do not really need this to work on the backend, even actions on client side elements do not allow that. In any case, my use case is the following:
- I have a TIMESHEET data type for users to log their working hours.
- I would like to generate a monthly invoice with all hours registered by each user per day (there could be 1, 2, 3, o more logs per day per user).
For that I have a backend workflow with the following inputs:
- Date (type date)
- Hours registered (type number)
- Users (type user)
This backend workflow uses these inputs to generate a line item in the invoice. So if I could schedule an API workflow on a list, which would be "do a seach for TIMESHEET’s: grouped by date, user (aggregating the amount of hours registered per TIMESHEET) that would create the 3 inputs (date, number and user) that I need for the backend workflow.
(grouping not allowed client side)
This is my particular use case, but I could see that being useful in other circumstances. And as you can see, I do not use at all the “grouping” on the backend, it is just to generate the inputs for the “schedule api workflow on a list” action triggered client side.