Json based Custom service API max size

(0) Share

Report

Posted on by Horvath Laszlo DAX

Hi,

I created a json-based custom service api interface.
Access: <d365fnourl>api/services/ServiceGroup/Service/PartnerInterface
If the size of the request is 40MB or less, the function will run. Above 40MB, I get the error message RequestEntityTooLarge.
Where can the limitations be set?

Regards

László

I have the same question (0)

All responses (3)

Answers (0)

MuthukumaranAX 2,903 on at

Like (0)

Report

can you check this post and see if it helps?

https://community.dynamics.com/forums/thread/details/?threadid=897679c4-1f8c-4a5d-9b9d-1bec4bd860ca

thanks

Was this reply helpful? Yes No
Kevin Xia Microsoft Employee on at

Like (0)

Report
Hi,

As the error message indicates, the amount of data requested is too large. You can solve this problem in several ways:

Compress data: Use data compression algorithms such as Gzip or Deflate to compress the data in the request. This can significantly reduce the size of the data and reduce the bandwidth required for transmission.

Use pagination or batch processing: If possible, break down larger requests into smaller ones. You can use pagination, iterations, or batch processing to handle large amounts of data. This helps distribute the size of the requests and improves the efficiency of processing.

Best regards,

Kevin

Was this reply helpful? Yes No
Suggested answer

Community member 2 on at

Like (0)

Report

You should check out https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/integration-overview

This will give you a general overall idea on what type of endpoint you should be using based on the general task you are trying to complete. Generally speaking an API should really be processing a single request at a time and should be a small quick payload. It sounds like you need to rethink your approach as you shouldn't be trying to send 40mb+ via a single api call. Doesn't matter what platform you are dealing with it sounds like you may be violating general web best practices. If you do want to stick to the json/soap api structure... Instead of processing the entire payload try breaking it down record by record.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Json based Custom service API max size

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

Json based Custom service API max size

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates