I make a suggestion, when using the
Bulk endpoints of Exact Online.
The Bulk Exact Online API endpoints do not support all filtering features available in the equivalent not bulked endpoint. That means that an Invantive client clause
WHERE to a bulk endpoint may do filtering
- API side if the filtering is available
- or on the client (Invantive) side if not available in the API
BulkTransactionLines enpoint :
Only the following filters are supported for this endpoint:
Account, CostUnit, CostCenter, Date, Division, Document, EntryID, EntryNumber, FinancialPeriod, FinancialYear, GLAccount, ID, InvoiceNumber, JournalCode, Modified, OrderNumber, Project, Status, TrackingNumber, Type, VATType, VATCode, YourRef
whereas on the Transactionlines enpoint support filtering on any fields.
Could that be a good idea that in querytool, Invantive could issue a warning before or after executing the statement to remind that the WHERE clause is using filters not supported in the enpoint?
See if it is wise in other command lines Invantive products.