Answers.Body: <p>Modifying field types in CiviCRM is bound to create problems later on (e.g. with upgrades), so I wouldn't do that.</p>
  
  <p>The straightforward approach would be to create a custom fieldset for relationships and add in a new custom field that is large enough for your data. I suspect there might be a few gotchas in terms of accessing this field, but if you're in Drupal, then the entity support in Drupal might solve this.</p>
  
  <p>Apropos of this, here's an article about Drupal that points to how important this kind of fieldable relationship entity can be:
  <a href="http://atendesigngroup.com/blog/drupals-weak-link" rel="nofollow">http://atendesigngroup.com/blog/drupals-weak-link</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-03T13:42:36.770Z
Answers.LastActivityDate: 2016-08-03T13:42:36.770Z
Answers.UserDisplayName: Alan Dixon
Body: <p>Is there a way to increase the size of the Relationship Notes field?</p>
  
  <p>In 4.6, it appears to be stored in the varchar(255) "description" column of the civicrm_relationship table. Nevertheless, Webform-CiviCRM integration let us use a textarea as a widget for this field, and now that the client has become accustomed to the idea of using this field for longer content.</p>
  
  <p>I tried simply increasing the column size in the database and flushing caches, but it does not seem to make any difference by itself; submitting the webform to create the relationship results in the same error:</p>
  
  <blockquote>
    <p>The CiviCRM "relationship create" API returned the error: "Value for description is 884 characters - This field has a maxlength of 255 characters." when called by function "preSave" on line 187 of wf_crm_webform_postprocess.inc with parameters: "Array ( [relationship_type_id] => 17 [is_active] => 1 [start_date] => now [description] => <em>884-character description went here</em> [contact_id_a] => 26305 [contact_id_b] => 13475 [is_permission_b_a] => 1 [is_permission_a_b] => 0 [check_permissions] => [version] => 3 ) "</p>
  </blockquote>
  
  <p>The site is a Drupal 7.44 / CiviCRM 4.6.19 site, with Webform 7.x-4.x-dev and Webform-CiviCRM Integration 7.x-4.15. The ability to add case relationships was <a href="https://www.drupal.org/node/2034097" rel="nofollow">added back in 7.x-3.x</a>.</p>
  
Tags: <webform-civicrm><relationships><4.6><fields>
Title: Expanding the Relationship Notes field
ThreadText: # Expanding the Relationship Notes field
  
  (Asked by: username_0 on 2016-07-27)
  
  Is there a way to increase the size of the Relationship Notes field?
  
  In 4.6, it appears to be stored in the varchar(255) "description" column of the civicrm\_relationship table. Nevertheless, Webform-CiviCRM integration let us use a textarea as a widget for this field, and now that the client has become accustomed to the idea of using this field for longer content.
  
  I tried simply increasing the column size in the database and flushing caches, but it does not seem to make any difference by itself; submitting the webform to create the relationship results in the same error:
  
  > The CiviCRM "relationship create" API returned the error: "Value for description is 884 characters - This field has a maxlength of 255 characters." when called by function "preSave" on line 187 of wf\_crm\_webform\_postprocess.inc with parameters: "Array ( [relationship\_type\_id] => 17 [is\_active] => 1 [start\_date] => now [description] => *884-character description went here* [contact\_id\_a] => 26305 [contact\_id\_b] => 13475 [is\_permission\_b\_a] => 1 [is\_permission\_a\_b] => 0 [check\_permissions] => [version] => 3 ) "
  
  The site is a Drupal 7.44 / CiviCRM 4.6.19 site, with Webform 7.x-4.x-dev and Webform-CiviCRM Integration 7.x-4.15. The ability to add case relationships was [added back in 7.x-3.x](https://www.drupal.org/node/2034097).
  
  **Tags:** webform-civicrm, relationships, 4.6, fields
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-08-03. Score: 2 | Accepted answer
  
  Modifying field types in CiviCRM is bound to create problems later on (e.g. with upgrades), so I wouldn't do that.
  
  The straightforward approach would be to create a custom fieldset for relationships and add in a new custom field that is large enough for your data. I suspect there might be a few gotchas in terms of accessing this field, but if you're in Drupal, then the entity support in Drupal might solve this.
  
  Apropos of this, here's an article about Drupal that points to how important this kind of fieldable relationship entity can be:
  <http://atendesigngroup.com/blog/drupals-weak-link>
  
  
  ---
  
  