Is there a hard character limit on the integration's HTTP response? I’ve noticed that text values exceeding 4,000 characters aren’t being returned—just wanted to confirm if this is a known constraint.
Also, while performing searches, it seems the maximum number of records returned is capped at 200. For example, when trying to retrieve information for 500 users including their addresses and phone numbers, we’re only getting data for 200 users. Is there a way to increase this limit or paginate through the results?
Discussion posts and replies are publicly visible
sanjuktab2257 said:I’ve noticed that text values exceeding 4,000 characters aren’t being returned—just wanted to confirm if this is a known constraint.
Where do you see this? I do not know of any limit in the HTTP response.
Search is limited. And paging is supported. The documentation provides a lot of guidance on this.
AFAIK, Appian does not have any hard limit on characters when it comes to integration objects. Refer here for the integration object response limits (5 MB).Appian supports pagination while we query or display search results or even in integrations if the Target API does have necessary batch size parameters to pass
The only limitation I've run into is related to Web API objects having a hard limit of 4,000 characters for the definition of the API object. I wound up having the API object determine which expression rules to call based upon some path / URL parameter logic, and then the json validation, business logic / write records / start processes / etc were all handled via the expression rules. Some of the API's would return very large packages to the caller, so there definitely wasn't a 4,000 character limit on the API response.
Furthermore, when I setup integrations to call BigQuery REST API's for a record sync, we would definitely receive more than 4,000 characters per response / batch. So I don't think there's an inherent 4000 character limit on Appian integration objects' responses.
We'll need more information about your API's and / or searches to understand where the limitation is coming from. 200 is a very arbitrary number for a limitation, and I wouldn't be surprised if a developer put this number somewhere in your Appian application's code simply because there wasn't a logical pagination limit to land on at the time.