I haven't used the Caliper API in production before, but if you have access to the SDK, you can deploy an extension as a custom endpoint and then query the DB as needed for transactions.

Here's a decent writeup for Transactions in the SDK docs: https://docs.q2developer.com/guides/database/transactions.html

When I needed to pull transaction data, I had an extension that queried the Backoffice API - Generated Transactions endpoint (via the DB object in my SDK extension). It was a periodic...

Thanks for your response, Trey.

The extension itself is a Periodic Entrypoint extension, so when this is deployed, it will generate in the background w/o any user interaction to initiate the job. We don't have any intention to offer this as something that can be generated from user interaction, either. The method I described above is the only way I could think of to test this in PTE and not need to wait for an automated job to kick off to see if my changes worked or not. I was hoping someb...

Totally guessing here, but have you tried removing the oninput="validateInputEvent(event)" line?

Thank you for the detailed response, Paden. I will take this back to my team and take appropriate action.

Much appreciated!

Thanks for the suggestion, Trey. What I ended up doing is capturing the form HTML and setting it to a variable on page load. Then, when the 'Go Back' button is clicked in the modal, I set the form HTML to the variable. This approach seems to work well