Hi All
I recently learned Groupby isn't delegable, despite not showing any warnings.
My use case is the following:
I have a parent list --> Conflict Check List TESTING APP
I have a child list --> Conflict Check Response TESTING APP
Conflict reference ID refers to the ID column in the Parent list
Used for an approval flow going around several users
Both are on Sharepoint Backend.
The parent list has all client info, that relates to the approval request.
The child list captures all the approval responses.
With({wFilteredChecksList: Filter('Conflict Checks List TESTING APP', 'Conflict Approval Status' = "Pending")},
With({wFilteredResponses: Filter(RenameColumns('Conflict Response List TESTING APP', "ID", "ResponseID"), 'Conflict Reference ID' in wFilteredChecksList.ID)},
With({wGroupedResponses: GroupBy(wFilteredResponses, "Conflict_x0020_Reference_x0020_I", "DATA")},
With({wUserNotPresentInGrouped: Filter(wGroupedResponses, Not(varUserEmail in DATA.'Approver Email'))},
Filter(wFilteredChecksList, ID in wUserNotPresentInGrouped.Conflict_x0020_Reference_x0020_I)))))
So I
1. Filter all the parent list records that have the status "Pending".
2. Rename the ID column in my child list to avoid conflict and filter the child list where 'Conflict Reference ID' has the same value as the parent "ID". (this way they relate to each other)
3.I Group all records in the child list that have the same 'Conflict Reference ID'.
4.Then I filter that data to show only the ones where the logged in user is not present
(this way, the logged in user sees which approvals are still 'pending' for him.)
(when a user submits his response, a record is added in the child list, so that makes his user email present in the 'Approver Email' column)
My Child list is going way above 2000 records but I didn't know GroupBy was't delegable.
Are there any known workarounds?
Kind regards & thank you in advance
