Can we get a list of any changes that were done and / or needed for our integration with the latest Quantify release. We have updated our databases with the latest release and now we are having issues with Jobsites and invoicing pushing to our ERP.
Hi mgray. It depends on what version you migrated from. All of the release notes are here: https://avontus.atlassian.net/wiki/spaces/ADH/pages/2240872456/Quantify
If you can show some sample code and the error(s) we can help you troubleshoot
Thanks for the quick response - yes we did notate the release notes as per you link before we did the update as we didn’t see anything specific in the list that would have changed our integration points.
I will get our developers to send more detail information of the errors we are seeing. Specifically with invoicing as we see that any invoices that have damages billed and/or additional charges included are erroring out now. As well as from the jobsite the Global Yes/No option seems to be the issue for our jobsite syncing.
As a further note and maybe this will help in determining the issues. Both our TEST database and our AUS database works with no issues - jobsites and invoicing is syncing to the ERP. It is however all other databases that seem to result is the errors. Could there be some server setup issues?
Please below error from our developer with regard to invoice processing. Note that we find this only for those invoices that have PRODUCT CHARGES (i.e. consumables, damages) but all other invoices are processing (recurring/new rentals and MOVs).
The web service call to Quantify to get the invoice by id is erroring out with the following error:
Avontus.Core.DataPortalException: DataPortal.Fetch failed (Invalid criteria when fetching movement) —>
Avontus.Core.Reflection.CallMethodException: DataPortal_Fetch method call failed —> System.Exception: Invalid criteria when fetching movement
- at Avontus.Rental.Library.Movement.DataPortal_Fetch(Criteria criteria)*
- at dm(Object , Object[] )*
- at Avontus.Core.Reflection.MethodCaller.CallMethod(Object obj, DynamicMethodHandle methodHandle, Object[] parameters)*
- — End of inner exception stack trace —*
- at Avontus.Rental.Library.Movement.DataPortal_Fetch(Criteria criteria)*
- at dm(Object , Object[] )*
- at Avontus.Core.Reflection.MethodCaller.CallMethod(Object obj, DynamicMethodHandle methodHandle, Object[] parameters)*
- at Avontus.Core.Reflection.MethodCaller.CallMethod(Object obj, DynamicMethodHandle methodHandle, Object[] parameters)*
- at Avontus.Core.Server.SimpleDataPortal.Fetch(Type objectType, Object criteria, DataPortalContext context)*
- — End of inner exception stack trace —*
- at Avontus.Rental.Library.Movement.DataPortal_Fetch(Criteria criteria)*
- at dm(Object , Object[] )*
- at Avontus.Core.Reflection.MethodCaller.CallMethod(Object obj, DynamicMethodHandle methodHandle, Object[] parameters)*
- at Avontus.Core.Reflection.MethodCaller.CallMethod(Object obj, DynamicMethodHandle methodHandle, Object[] parameters)*
- at Avontus.Core.Server.SimpleDataPortal.Fetch(Type objectType, Object criteria, DataPortalContext context)*
- at Avontus.Core.DataPortal.Fetch(Type objectType, Object criteria)*
- at Avontus.Core.DataPortal.Fetch[T](Object criteria)*
- at Avontus.Rental.Library.Movement.GetMovement(Guid purchaseID, MovementGetAction action, Boolean includeMasterList)*
- at Avontus.Rental.Wrapper.InvoiceService.GetById(String invoiceId)*
Hi mgray. Thanks for the exception message. The exception originates in this code, which isn’t a part of Quantify (it calls Quantify code though). Can you have your developer look into this code?
If they are having trouble finding out why the code that calls Quantify is failing within that code, you can send a code snippet and we’ll see if we can try and reproduce on our end.