Page 1 of 1

Error deleting debtor delivery address

PostPosted: Fri Nov 25, 2022 11:20 am
by aaron_bonntech
Hi,

When calling the Delete Debtor Delivery Address API in Jiwa I am getting an error. Any clue about this error?

Thnaks.

"{"ResponseStatus":{"ErrorCode":"Exception","Message":"One or more errors occurred.\r
\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
","StackTrace":"[DebtorDeliveryAddressDELETERequest: 11/24/2022 11:37:02 PM]:\n[REQUEST: {DebtorID:XXXXX,DeliveryAddressID:XXXXX}]\nSystem.Exception: One or more errors occurred.\r
\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
Object reference not set to an instance of an object.\r
\r
at JiwaFinancials.Jiwa.JiwaApplication.JiwaCollection`1.iSave() in C:\\VSTS\\Jiwa 7\\07.02.00\\JiwaApplication\\JiwaCollection.vb:line 547\r
at JiwaFinancials.Jiwa.JiwaApplication.JiwaCollection`1.Save() in C:\\VSTS\\Jiwa 7\\07.02.00\\JiwaApplication\\JiwaCollection.vb:line 490\r
at JiwaFinancials.Jiwa.JiwaDebtors.Debtor.iSave() in C:\\VSTS\\Jiwa 7\\07.02.00\\JiwaDebtors\\Debtor.vb:line 3888\r
at JiwaFinancials.Jiwa.JiwaApplication.BusinessLogic.Maintenance.Save() in C:\\VSTS\\Jiwa 7\\07.02.00\\JiwaApplication\\BusinessLogic\\Maintenance.vb:line 433\r
at JiwaFinancials.Jiwa.JiwaServiceModel.DebtorDeliveryAddressServices.Delete(DebtorDeliveryAddressDELETERequest request) in c:\\ProgramData\\Jiwa Financials\\Jiwa 7\\7.2.1\\JAPILive\\cedar-srv-dc\\JiwaCedarHosp\\Plugins\\APIUser\\Compile\\REST API\\REST API.cs:line 9870\r
at lambda_method(Closure , Object , Object )\r
at ServiceStack.Host.ServiceExec`1.<>c__DisplayClass3_0.b__0(Object service, Object request)\r
at ServiceStack.Host.ServiceRunner`1.d__13.MoveNext()","Errors":[]}}"

Re: Error deleting debtor delivery address  Topic is solved

PostPosted: Fri Nov 25, 2022 11:43 am
by Mike.Sheen
I've just tested this with 7.2.1 SR14 and do not get such an error - it deletes the delivery address when I visit Debtors/{DebtorID}/DeliveryAddresses/{DeliveryAddressID} after authentication.

If you have any custom plugins, I would try creating a demo data, and configuring an API instance against that demo database and confirming yourself that your environment has no issue deleting a debtor delivery address. Then I'd identify your custom plugins in the problem database and import them one by one, testing the delete via the API after restarting the API service after each import.

Re: Error deleting debtor delivery address

PostPosted: Mon Nov 28, 2022 10:32 am
by aaron_bonntech
Hi,

Yes Please,

One record was successfully deleted when I checked this morning. But subsequent reports get the same error.

Thanks