Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIRST/LAST does not properly filter by lookup item (and potential issues with SOQL where clause) #80

Closed
jamessimone opened this issue Apr 19, 2021 · 0 comments · Fixed by #81

Comments

@jamessimone
Copy link
Owner

jamessimone commented Apr 19, 2021

Reported by Katherine West -

  • FIRST/LAST does not constrain the SOQL query by lookup item - easy fix
  • FIRST/LAST may not be correctly getting the SOQL where clause - still need to check on this one
  • delete operations on FIRST/LAST need to exclude current items
  • return human-readable error message if order by is not passed for first/last from flow
  • still run FIRST/LAST if current iteration's items get filtered out via the calc item where clause (since, like AVERAGE, FIRST and LAST are full recalcs every time)
jamessimone added a commit that referenced this issue Apr 19, 2021
…ade by rollup calculators, as well as fixing a bug with FIRST/LAST operations where the lookup clause was not being properly passed through
jamessimone added a commit that referenced this issue Apr 19, 2021
…ST/LAST * return human-readable error message when order by is not included from flow * correctly run rollup when calc item where clause would exclude the only items passed
jamessimone added a commit that referenced this issue Apr 21, 2021
* Initial refactor necessary to start supporting rollups all the way to ultimate parent for hierarchy/self-referential lookups like Account.ParentId

* Fixes #80 by correctly passing calc item where clause to re-queries made by rollup calculators, as well as fixing a bug with FIRST/LAST operations where the lookup clause was not being properly passed through

* Continued fixes for #80: 

* properly support delete operations for FIRST/LAST 
* return human-readable error message when order by is not included from flow 
* correctly run rollup when calc item where clause would exclude the only items passed

* Finished wiring hierarchical rollups into the grandparent rollup framework

* Additional consideration for #80 zero-based where clause filtering
jamessimone added a commit that referenced this issue Apr 22, 2021
…ate lookup items if the current value would be excluded due to the calc item where clause, but the old item's value would not be excluded.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant