SDATA Call returns a max of 200 rows

This question is not answered

Hi All,

Does anyone know if the max count value can be increased beyond 200.

If I specify a greater number in the SDATA call it seems to be capped at 200.

e.g. http://servername/sdata/crmj/sagecrm/-/vCustomView?count=500

Please advise.


All Replies
  • SDATA is normally capped at 100 as per

    If you required anything over that and you should use paging via the startindex property. i.e.


    Sage CRM specialist and all round fan! Please feel free to follow me on twitter @dannycrm

  • Hi Daniel,

    Thank you for the swift response.

    That's a shame I was hoping that the default max value could be overridden :(

    Do you know if there is any config files where this can be increased or is it hard-coded in one of the .dll files?


  • I am not specifically sure to be honest. Normally the max is coded into the service to maintain performance based on the data its serving. Maybe Jeff will be able to advise further?

    Sage CRM specialist and all round fan! Please feel free to follow me on twitter @dannycrm

  • I sort of feel redundant answering any questions that Danny has already responded to.

    You've seen reference to the default count of 100 and the maximum return of 200.

    And you know how to use the count variable

    http://localhost/sdata/crmj/sagecrm/-/company?startIndex=1&count=10&where=comp_name like 'A%'

    http://localhost/sdata/crmj/sagecrm/-/company?startIndex=1&count=10&where=comp_name like 'A%' and comp_type eq 'customer%'&includeSchema=true

    http://localhost/sdata/crmj/sagecrm/-/company?startIndex=1&count=10&where=comp_name like 'A%' or comp_name like 'C%'

    http://localhost/sdata/crmj/sagecrm/-/company?startIndex=1&count=10&where=comp_name like 'A%'&includeSchema=true&orderBy=comp_name desc

    But is this count maximum changeable?

    I think the answer is NO.  Under

    C:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmj\WEB-INF

    The only configurable options for us are within the Log4j.xml.  

  • Thanks Daniel and Jeff :)

    I have checked out the Log4j.xml file and your are right that it doesn't look like this is configurable.

    It would have been nice to have this as a configurable option, shame as it is probably a hard-coded limit in the Tomcat service.

    Thanks again, Julian