Is it possible to increase the performance of an areas request ?

[f-llewellyn]

Summary
When trying to fetch Reapit areas in large instances, the request takes too long and causes our back end to timeout. This is due to the large amount of unnecessary data returned. All we require is area name and id.

Detail and or supporting links and screenshots
When calling the reapit areas endpoint, an attribute of the returned objects is an areas field that contains a list of co-ordinates dictating the geographical location of the area. In certain, large instances, these arrays can be so large that they slow down the requests significantly. Due to the amount of time taken, our backend times out. It looks as if the requests can take upwards of a minute when accounting for each page, as shown here:

The reason we make this request is to allow agents to select an area when sending applicant records. For this, the only information we need from these requests is the area name and id. To cut down on unnecessary data, we already filter by officeId.

Is it possible to only request area name and id fields, or make the request in a more performant way?

[AshDeeming]

Migrated to internal issue: PBI-5865

[AshDeeming]

Hi @f-llewellyn
Please note that following an investigation, there is a bigger piece of work to update the structure of the table in the CRM

In the short term we’d recommend you look to reduce the size of the request (to 100 for example)