Merge branch 'patch-1'
[#49] Improve help text for custom fields mapping
This commit is contained in:
commit
e01b1ef8f3
1 changed files with 1 additions and 0 deletions
|
@ -58,6 +58,7 @@
|
||||||
{ts domain="de.systopia.twingle"}<p>Map Twingle custom fields to CiviCRM custom fields using the following format (each assignment in a separate line):</p>
|
{ts domain="de.systopia.twingle"}<p>Map Twingle custom fields to CiviCRM custom fields using the following format (each assignment in a separate line):</p>
|
||||||
<pre>twingle_field_1=custom_123<br />twingle_field_2=custom_789</pre>
|
<pre>twingle_field_1=custom_123<br />twingle_field_2=custom_789</pre>
|
||||||
<p>Always use the <code>custom_[id]</code> notation for CiviCRM custom fields.</p>
|
<p>Always use the <code>custom_[id]</code> notation for CiviCRM custom fields.</p>
|
||||||
|
<p>This only works for fields that Twingle themselves provide in the <code>custom_fields</code> parameter, not for any parameters; e.g. <code>user_extrafield</code> always ends up in a note.</p>
|
||||||
<p>Only custom fields extending one of the following CiviCRM entities are allowed:</p>
|
<p>Only custom fields extending one of the following CiviCRM entities are allowed:</p>
|
||||||
<ul>
|
<ul>
|
||||||
<li><strong>Contact</strong> – Will be set on the Individual contact</li>
|
<li><strong>Contact</strong> – Will be set on the Individual contact</li>
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue