We just hit a wall for one of our customers. They have 993 columns/properties on their deals object and when we try to do search over crm/v3/objects/deals/search we get 400 Bad request back. After some testing we managed to do a succesful call using the first 696 columns producing a payload of 43532 bytes.
Is this limit on purpose? If so a nicer error message would be appreciated!
If it is on purpose what is the recommended course of action? To make several queries with subsets of the property list in order to cover everything?
Hello @dennisedson - there is sadly nothing except the status code 400. (Which makes sense I guess - if it was a handled error I assume it would be another status code.)
Hello @fredrik_ruben , unfortunately there is not much we can do without an error code. I have alerted the product team to this and if I receive any news on this, I will make sure to respond here.
