Export is a kind of weird & wonderful setting that is undocumented. It affects
whether fields are available by default in export & search, sometimes.
Generally I would say all 'user facing fields' should be set to export or somewhere
or other we will wind up hacking around it. I recently removed a lot
of code for payment_instrument_id that was just compensating for this var being
false rather than true.
*
* Generated from xml/schema/CRM/Activity/Activity.xml
* DO NOT EDIT. Generated by CRM_Core_CodeGen
- * (GenCodeChecksum:60fe612216c0096685be3e555a4772c3)
+ * (GenCodeChecksum:a530f1fb1a27c5a15b5d138732b4c581)
*/
require_once 'CRM/Core/DAO.php';
require_once 'CRM/Utils/Type.php';
'where' => 'civicrm_activity.status_id',
'headerPattern' => '/(activity.)?status(.label$)?/i',
'dataPattern' => '',
- 'export' => false,
+ 'export' => true,
'table_name' => 'civicrm_activity',
'entity' => 'Activity',
'bao' => 'CRM_Activity_BAO_Activity',
<uniqueName>activity_status_id</uniqueName>
<title>Activity Status</title>
<import>true</import>
- <export>false</export>
+ <export>true</export>
<headerPattern>/(activity.)?status(.label$)?/i</headerPattern>
<type>int unsigned</type>
<comment>ID of the status this activity is currently in. Foreign key to civicrm_option_value.</comment>