Author Topic: What's the logic of the custom_xx_yy param (on 3.3) ? (Read 13335 times)

xavier · January 30, 2011, 12:45:48 pm

Hi,

The api compatibility has been broken. What's the benefit of the new _yy (and what does it represent?).

How complicated whould it be to be able to set an "API friendly" name ? ie. having custom_special is nicer to work with than custom_34_238

Any suggestion to make it easier to find the mystery numbers more than welcome...

X+

Donald Lobo · January 30, 2011, 05:36:30 pm

i think we introduced this protocol since we introduced multiple custom values, which was in 2.x or so

the number are the ids in the custom field table and the table that stores the values

you can potentially change the name to

group_name:field_name , but will then need to return the value table id in an array

lobo

xavier · January 31, 2011, 01:52:17 am

Hi,

At least seen from the API, this change was more recent (after 3.0).

What I'm worried about (beside readability of the code) is that the second number is going to vary from record to record (as it does/did do for the field id on the html forms).

Is this the case or is custom_xx_yy (as seen on the html form id) always going to be the same two numbers on the API and I can use them as return on the contact_get api or as param on the contact_add and contact_create ?

X+

CiviCRM Community Forums (archive)

News:

Author Topic: What's the logic of the custom_xx_yy param (on 3.3) ? (Read 13335 times)

xavier

What's the logic of the custom_xx_yy param (on 3.3) ?

Donald Lobo

Re: What's the logic of the custom_xx_yy param (on 3.3) ?

xavier

Re: What's the logic of the custom_xx_yy param (on 3.3) ?