Author Topic: Custom set/field: we should expose the name (Read 502 times)

xavier · May 26, 2011, 01:41:31 am

Hi,

so it seems that the name is automatically generated munging the label. to solve the api and import issues when the name is too long, I'd suggest

1) to expose the name of the set/group
if empty set name = munge (label)
checking that the result is sane (eg. < 20 chars)

2) to expose the name of the field
if empty, field name = set.name+"_"+ munging(label)

checking that the result is sane (eg. < 30 chars)

Where are the field/group name used today ? to generate the name of the column and "only" that ?

X+

Donald Lobo · May 26, 2011, 12:06:00 pm

From the UI it is autogenerated and not changed

from the API the name is used if passed in, else its autogenerated

Once the group/field is created, the name is not changed (there have been bugs in this code, but hopefully most/all of them fixed in 3.4.2)

The current character limit is 64 chars on the name

lobo

CiviCRM Community Forums (archive)

News:

Author Topic: Custom set/field: we should expose the name (Read 502 times)

xavier

Custom set/field: we should expose the name

Donald Lobo

Re: Custom set/field: we should expose the name