This site has been archived. Please visit help.fulcrumapp.com for our new support documentation and contact information.

Error "closed changeset"

Paul Wickman's Avatar

Paul Wickman

15 May, 2016 05:25 PM

Hello,

For several years we've been happily updating records in Fulcrum via the API. Recently though (last ~2 weeks) we are no longer able to update records instead receiving a 422 error from the REST endpoint saying, "closed changeset and cannot be updated". Wondering if their has been a change to the API recently. Is there another flag or setting I need to touch in order to update records via the API?

{:error=>{:status=>422, :message=>{"record"=>{"errors"=>{"changeset_id"=>["is a closed changeset and cannot be used"]}}}}}

Particulars in one case:

Organization: CRH
App: Data Collection Checklist - Philippines
Record ID: c0f1a858-bb7a-42fe-87f3-7fdc85fcae75

  1. Support Staff 1 Posted by Alex Helms on 16 May, 2016 02:18 PM

    Alex Helms's Avatar

    Hello Paul,

    We recently added the changeset ids to the payload obtained through the API (~2 weeks ago). If you are uploading data through the API, removing the changeset id should address the issue.

    Every time a data is synced from the mobile devices to the server, a record is edited/created on the web app, or data is imported into Fulcrum a changeset id is created. You can not populate data into an existing changeset and this is why you are getting this error.

    Thanks,
    Alex

  2. 2 Posted by Paul Wickman on 16 May, 2016 04:49 PM

    Paul Wickman's Avatar

    Thanks, Alex. We’ll update our API calls accordingly.

    Is there a developers mailing list we can be on so we’re notified ahead of times of those sorts of changes?

    Thanks,
    -Paul

  3. Support Staff 3 Posted by Alex Helms on 16 May, 2016 04:59 PM

    Alex Helms's Avatar

    There is not, but I will share your interest in one with the development and management teams.

  4. 4 Posted by Paul Wickman on 16 May, 2016 05:10 PM

    Paul Wickman's Avatar

    Thanks, Alex. Given that we’ve built up some considerable dependence on Fulcrum (and technically are consider a partner) it would definitely be good to know about things coming down the pike that potentially affect our operations.

    Thanks again for the quick reply.
    Paul

  5. 5 Posted by Bryan McBride on 16 May, 2016 05:21 PM

    Bryan McBride's Avatar

    Hey Paul,

    We rarely make changes to the API that impact workflows like this, and are working on a fix so you shouldn't have to remove that changeset_id property. This was an unintentional bug that was accidentally introduced. That being said, we are working on implementing an API changelog in our developer docs and will notify developers of any potential issues with future API changes.

    Thanks for your patience working with us to get this resolved!

    -Bryan

  6. 6 Posted by Paul Wickman on 16 May, 2016 05:38 PM

    Paul Wickman's Avatar

    Thanks, Bryan. If the fix in imminent (today/tomorrow) then we’ll hold off making any changes on our end.

    -pjw

  7. 7 Posted by Bryan McBride on 17 May, 2016 10:50 PM

    Bryan McBride's Avatar

    Hey Paul,

    We just pushed that API fix. Thanks for your patience.

  8. 8 Posted by Paul Wickman on 17 May, 2016 11:21 PM

    Paul Wickman's Avatar

    Thanks, Brian. I'll check the sync logs in the morning.

    Paul Wickman

  9. 9 Posted by Paul Wickman on 18 May, 2016 06:22 PM

    Paul Wickman's Avatar

    Thanks, Bryan. Things look good again on our end.

    -Paul

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac