From 61f45034c6dd83cc714f36d1e8152397063874ba Mon Sep 17 00:00:00 2001 From: Jens Schuppe Date: Thu, 13 Jun 2024 13:03:17 +0200 Subject: [PATCH] Update help text for custom field mapping configuration option to reflect that all parameters are supported. --- templates/CRM/Twingle/Form/Profile.hlp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/templates/CRM/Twingle/Form/Profile.hlp b/templates/CRM/Twingle/Form/Profile.hlp index b8d67a4..a8efdc5 100644 --- a/templates/CRM/Twingle/Form/Profile.hlp +++ b/templates/CRM/Twingle/Form/Profile.hlp @@ -62,10 +62,10 @@ {/htxt} {htxt id='id-custom_field_mapping'} - {ts domain="de.systopia.twingle"}

Map Twingle custom fields to CiviCRM custom fields using the following format (each assignment in a separate line):

+ {ts domain="de.systopia.twingle"}

Map Twingle custom fields to CiviCRM fields using the following format (each assignment in a separate line):

twingle_field_1=custom_123
twingle_field_2=custom_789

Always use the custom_[id] notation for CiviCRM custom fields.

-

This only works for fields that Twingle themselves provide in the custom_fields parameter, not for any parameters; e.g. user_extrafield always ends up in a note.

+

This works for fields that Twingle themselves provide in the custom_fields parameter, and for any other parameter (e.g. user_extrafield)

Only custom fields extending one of the following CiviCRM entities are allowed: