Hi all,
I am intending to use the Quickfile Journal API functions to mass-create transactions.
I have so far discovered:
Journal_Create allows me to create Journal entries.
I can create Journals with two or more entries, for as long as the debit and credit sums balance out.
They show up in the Journals part of the Web UI just fine and exactly as they are intended.
Journal_Delete doesn’t let me delete the very created journal , and fails with XML exception:
{
"Errors": {
"Error": [
"3The targetNamespace parameter 'http://www.QuickFile.co.uk' should be the same value as the targetNamespace '' of the schema.",
"1The 'http://www.QuickFile.co.uk:Journal_Delete' element is not declared.",
"2The 'http://www.QuickFile.co.uk:Header' element is not declared.",
"3The 'http://www.QuickFile.co.uk:MessageType' element is not declared.",
"4The 'http://www.QuickFile.co.uk:SubmissionNumber' element is not declared.",
"5The 'http://www.QuickFile.co.uk:Authentication' element is not declared.",
"6The 'http://www.QuickFile.co.uk:AccNumber' element is not declared.",
"7The 'http://www.QuickFile.co.uk:MD5Value' element is not declared.",
"8The 'http://www.QuickFile.co.uk:ApplicationID' element is not declared.",
"11The 'http://www.QuickFile.co.uk:Body' element is not declared.",
"12The 'http://www.QuickFile.co.uk:JournalDetails' element is not declared.",
"13The 'http://www.QuickFile.co.uk:JournalReference' element is not declared."
]
}
}
This is irrespective of the Journal being unlocked, locked, nor does the number of journal entries (whether debit or credit) matter.
Journal_Get response fails with:
single-line (i.e. two JournalLine entries for debit and credit)
{
"Errors": {
"Error": [
"Internal Error: Unexpected end of file has occurred. The following elements are not closed: Journal_Get. Line 23, position 10."
]
}
}
multi-line (i.e. more than two JournalLine entries for debit and credit)
{
"Errors": {
"Error": [
"Internal Error: Unexpected end of file has occurred. The following elements are not closed: Journal_Get. Line 198, position 10."
]
}
}
Quite apparently this is a server side fault as the latter is a very large journal (in fact, a live system year-end journal) hence the line numbers in the error messages change according to the size of the journal.
Support, to the rescue, please!