Skip to main content
Solved

Web Service Endpoints return empty body on one tenant


rcreasy
Varsity I
Forum|alt.badge.img

I am working on an API integration that stopped working. I have narrowed the problem down to - endpoints on one tenant return an empty body in the response.

I tested outside of my application using Insomnia to test results from endpoints. With everything equal other than the tenant, 5 different endpoints returned an empty body on one tenant, and worked as expected on another tenant in the same instance.

Someone else did install a customization package between when things were working and when things broke. So, I am suspicious that the cause may lie in that package.

I am relatively new to Acumatica. So, I don’t know where to begin looking. 
Can anyone point me in the right direction?

Best answer by rcreasy

@zfebert56 It turns out that a configuration done by someone else caused the issue. That person corrected. But, I don’t know the details.

Thanks for reading my post and offering suggestions.

View original
Did this topic help you find an answer to your question?

4 replies

Zoltan Febert
Jr Varsity I
Forum|alt.badge.img+3

I would go to that screen where your endpoint points to and see if there is any data there.

What is the HTTP status when you get the empty body?


rcreasy
Varsity I
Forum|alt.badge.img
  • Author
  • Varsity I
  • 73 replies
  • July 14, 2023
zfebert56 wrote:

I would go to that screen where your endpoint points to and see if there is any data there.

What is the HTTP status when you get the empty body?

@zfebert56 sorry, should have mentioned - 200
For testing I just look up a customer by CustomerID - The customer ID definitely exists, and I can access it on the screen.

Additionally, the customer list on the non-working tenant is a duplicate of the customer list on the working tenant.


Zoltan Febert
Jr Varsity I
Forum|alt.badge.img+3

What happens if you try to get all customers, instead of filtering by CustomerID?


rcreasy
Varsity I
Forum|alt.badge.img
  • Author
  • Varsity I
  • 73 replies
  • Answer
  • July 18, 2023

@zfebert56 It turns out that a configuration done by someone else caused the issue. That person corrected. But, I don’t know the details.

Thanks for reading my post and offering suggestions.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings