Skip to content

Dave Conlin

← Customer Feedback for Xero API

My feedback

1 result found

  1. Fix broken linq count() processing on anything that is pagged like journals. Count is defined as the nuber of records, and cannot be pagged.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Accounting API » Journals  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Dave Conlin supported this idea  · 
    An error occurred while saving the comment
    Dave Conlin commented  · 

    I agree that the ability to find out how many things there are in total is really important.

    When you're batching/showing a user a large amount of information, it's really important to be able to give them an idea of the scale of the operation (progress bars, page numbers etc)

    Not sure that the implementation has to be "make the c# api return the right value for count", you could return some information as part of the query about the query stats. RavenDB is a pretty good example of how to make the second one work pretty well:

    http://ravendb.net/docs/client-api/querying/paging

    You could just slip in some extra information in the xml doc, outside the results list.

    Anyway, implementation isn't that important, but I do think that when you return paginated results, it's important to be able to find out how many there are, not just say "carry on getting new pages until there are none left"

Feedback and Knowledge Base

(thinking…)