Author Topic: Issue with API change in 4.2.2 (Read 603 times)

SarahG (FountainTribe) · October 02, 2012, 03:18:05 pm

I am calling the Participant API from JavaScript in order to change the participant status, such as from registered to cancelled. My call is

cj().crmAPI('Participant','update',{'version' :'3', 'participant_id' :participant_id_parm, 'status_id' :cancel_status_id}
,{callBack: function(result,settings){

This worked under CiviCRM 4.1.5. But when I upgraded to version 4.2.2, it returned the error message "fee_amount is not a valid amount:"

So I changed the call to
cj().crmAPI('Participant','update',{'version' :'3', 'participant_id' :participant_id_parm, 'status_id' :cancel_status_id, 'fee_amount' :'15' }
,{callBack: function(result,settings){

And it worked. BUT, why is the fee_amount now a required parameter? I do not have any interest in updating the fee amount, and in many cases the event was not a paid event anyhow.

xavier · October 03, 2012, 03:16:50 am

Hi,

Code: [Select]

cj().crmAPI('Participant','update',{'version' :'3', 'participant_id' :participant_id_parm, 'status_id' :cancel_status_id}

FYI, the version is optional on the ajax calls (and defaults to 3), and try to use id instead of participant_id, tends to makes more readable what is the primary key IMO.

Update was a read+create, it might be that the red format changed (I have had issues with the decimal separator localisation for instance).

Can you try 'create' instead of 'update' (with all the params staying identical) ?

Eileen · October 03, 2012, 03:02:43 pm

Hi Sarah - all events are saved as price sets now so you might need to look at how these are recorded when created through the front end & see what changes there are to the how the data is stored.

CiviCRM Community Forums (archive)

News:

Author Topic: Issue with API change in 4.2.2 (Read 603 times)

SarahG (FountainTribe)

Issue with API change in 4.2.2

xavier

Re: Issue with API change in 4.2.2

Eileen

Re: Issue with API change in 4.2.2