Author Topic: Should we get empty values ? (Read 746 times)

xavier · May 08, 2011, 01:36:37 am

Hi,

When using an api.get, the number of attributes might vary for each record, depending if this field is empty in the DB.

For instance, the first contact might have a 'email'=>'test@demo.org' but not 'phone', while the second will have a 'phone', no email, but a 'country'.

For my csv export, it means that the number of cell for each line is different, obviously not a good solution.

I am wondering if it wouldn't be better to have a mode that returns the same number of fields (and create empty fields if they are empty instead of skipping them, and have no clue of where to modify it.

What do you think, and any suggestion ?

X+

I have no idea

Eileen · May 08, 2011, 01:57:54 pm

My guess is this mainly applies to contact api? As it is the main api that gets 'stuff' from other entities? I suspect anything that works off one BAO does return the same fields empty or otherwise. In which case returning even if empty is the de facto standard

xavier · May 08, 2011, 02:20:28 pm

For instance the relationshiptype seems to skip.

I will modify csv/export see if I can spot easily something

X+

Erik Hommel · May 08, 2011, 11:15:49 pm

Empty ones rather than skipping would make more sense to me.

CiviCRM Community Forums (archive)

News:

Author Topic: Should we get empty values ? (Read 746 times)

xavier

Should we get empty values ?

Eileen

Re: Should we get empty values ?

xavier

Re: Should we get empty values ?

Erik Hommel

Re: Should we get empty values ?