Titanium JIRA Archive
Appcelerator Community (AC)

[AC-2497] ACS Event Update - Custom Data Field Not Being Updated

GitHub Issuen/a
TypeBug
Priorityn/a
StatusClosed
ResolutionNeeds more info
Resolution Date2013-04-04T20:40:32.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsTitanium SDK & CLI
LabelsACS, Custom, Event, Field, Update
ReporterBruce Parr
AssigneeShak Hossain
Created2013-01-12T10:47:28.000+0000
Updated2016-03-08T07:41:33.000+0000

Description

Updating an ACS event custom field returns status 200 but fails to update the event data. Example Code: var custom_data = { toLawEnforcement:true //boolean custom field in ACS } Cloud.Events.update({ event_id : eventID, custom_data: custom_data }, function(e) { Ti.API.log(JSON.stringify(e)); } ); Example Debug Data from ACS { "custom_data" => "{"toLawEnforcement":true}", "event_id" => "50df0018e0b1ba1a59000866", "ti_analytics" => "{"id":"C5E5A427-5F5A-4815-B8BB-80801E57F5EF","mid":"74478444-DCD9-4DFD-B5A1-324FBD7F6585","aguid":"13cd9f18-adc0-469e-8f14-2d2f2c8cc311","event":"cloud.events.update","deploytype":"development","sid":"CE63F3D2-F16F-421D-B66A-B807EF0E57C6"}", "suppress_response_codes" => "true", "oauth_consumer_key" => "xxxxxxxxxxxxxxxxx", "_session_id" => "qbQ4U6iLK2RCjY1nV4fy87IJ6JY", "controller" => "events", "action" => "update", "version" => "v1", "format" => "json" } Despite this, the custom field data remains false. I have tried as both boolean and string.

Comments

  1. Alan Leard 2013-01-26

    Please modify your call to:
       Cloud.Events.update({ event_id : eventID, custom_fields: custom_data }, function(e) { Ti.API.log(JSON.stringify(e)); }
       );
       
    This should work. Please confirm.
  2. Shak Hossain 2013-12-07

    Hi Bruce, We have not heard back from you since you posted the issue. Not sure if this is still throwing error in your app. If so, please send us the details so that we can take next necessary step to fix. If we don't hear back, we will assume the issue is no longer valid and close it.
  3. Shak Hossain 2013-12-28

    Closing as we got no further response from Bruce.

JSON Source