Giving the journal endpoint the same set of parameters as the GET for manual journals would solve this problem. Specifically being able to use a WHERE parameter on the journal GET.
We have a few use cases for this.
1. Reporting the full content of an arbitrary nominal over an arbitrary period.
2. Consolidating entities by copying transactions into a pesudo group entity. Having a more refined way of pulling all journals in user definable segments (rather than just an offset) would be helpful.
Ryan
supported this idea
·
Giving the journal endpoint the same set of parameters as the GET for manual journals would solve this problem. Specifically being able to use a WHERE parameter on the journal GET.
We have a few use cases for this.
1. Reporting the full content of an arbitrary nominal over an arbitrary period.
2. Consolidating entities by copying transactions into a pesudo group entity. Having a more refined way of pulling all journals in user definable segments (rather than just an offset) would be helpful.