Separate user stories have been created for the GET batch and GET transaction distribution endpoints. The first one will be released first, the second one raises some architectural concerns and may not be addressed in the current environment, will update as we learn more.
To expand on this using details from Gerard's Support case, he is using the 'Transaction Distribution List' endpoint from the General Ledger API. One of its inputs is batch_id, but batch_number would be helpful as well, because the Financial Edge web view only allows query on batch_number. The other endpoints that have an input of batch_id would be more convenient/accessible if batch_number is added as an input parameter.
Separate user stories have been created for the GET batch and GET transaction distribution endpoints. The first one will be released first, the second one raises some architectural concerns and may not be addressed in the current environment, will update as we learn more.
To expand on this using details from Gerard's Support case, he is using the 'Transaction Distribution List' endpoint from the General Ledger API. One of its inputs is batch_id, but batch_number would be helpful as well, because the Financial Edge web view only allows query on batch_number. The other endpoints that have an input of batch_id would be more convenient/accessible if batch_number is added as an input parameter.