We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
voidInvoice() and voidPayment() are not documented yet: 1a5a62a
There's also some useful info on voiding in this issue, that would be useful in the main readme: #43
Also, it seems "void" is an acceptable operation to provide to Batch Operations (which is useful..., but not documented).
For voiding payments using Batch Operations, it seems you can't use the "void" operation however. Instead you need to specify:
operation: "update" optionsData: "void"
https://community-intuit.force.com/developer/s/question/0D50f00005E4WI6/how-do-i-void-payments-through-the-batch-endpoint-of-the-api
(I'm not sure if you want to handle that case within the library, or just document it..)
If I get time in the coming weeks - I'll try put together a PR for these documentation updates ... but at least they are visible here in the meantime.
The text was updated successfully, but these errors were encountered:
#202
Sorry, something went wrong.
No branches or pull requests
voidInvoice() and voidPayment() are not documented yet:
1a5a62a
There's also some useful info on voiding in this issue, that would be useful in the main readme:
#43
Also, it seems "void" is an acceptable operation to provide to Batch Operations (which is useful..., but not documented).
For voiding payments using Batch Operations, it seems you can't use the "void" operation however. Instead you need to specify:
https://community-intuit.force.com/developer/s/question/0D50f00005E4WI6/how-do-i-void-payments-through-the-batch-endpoint-of-the-api
(I'm not sure if you want to handle that case within the library, or just document it..)
If I get time in the coming weeks - I'll try put together a PR for these documentation updates ... but at least they are visible here in the meantime.
The text was updated successfully, but these errors were encountered: