"current_revision" in "Filter items" operation gone

Answered

Comments

4 comments

  • Christian Holm

    Hi Jesper

    That was an ill change on my part. It will be back within the next 30 minutes.

    Going forward it would be good to use the created_by, created_on and created_via directly on the items returned, instead of using the revision objects.

    Christian

    0
    Comment actions Permalink
  • Jesper Lund Nielsen

    Hi Christian

    Thank you very much.

    I do have looked at the created_on and created_via but I can't see that this will give me the same information as current_revision can.

    I need to know who made the latest change, no matter what field it was.

    created_by gives me information about the user who created it in first place = no good.

    created_via gives me information about whether it was created via Podio or via Excel or something else.

    So... how to do it, if I can't use current_revision? I'm willing to change my code, I just need the same result as before.

    0
    Comment actions Permalink
  • Jesper Lund Nielsen

    Just a thought: If you need to make changes in your API, how about implementing some kind of API versioning.

    Lets say, the current API is v1 stable and the one you make changes in is v2 beta, where you can make new operations or changed responses.

    MailChimp eg. does this, which works great:  http://apidocs.mailchimp.com/api/

    0
    Comment actions Permalink
  • Christian Holm

    Hi Jesper

    We also do that on a method scale, but sometimes we do tweak existing API calls. This however was a bad change, hence the revert.

    Christian

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk