Answers.Body: <p>When you first create a custom group and it does not yet contain any data (e.g. no custom records have been saved for any contact) you are allowed to change anything. Once data exists, it is more restrictive to prevent data loss.</p>
  <p>However, in checking this I discovered a bug which was causing it to act stricter than it should. The logic is supposed to be that the maximum can be increased but not decreased. The bug was preventing it from being changed at all. Here is the fix: <a href="https://github.com/civicrm/civicrm-core/pull/27916" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/pull/27916</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-10-24T17:13:11.673Z
Answers.LastActivityDate: 2023-10-24T17:13:11.673Z
Answers.UserDisplayName: Coleman
Body: <p>It turns out one can only edit the &quot;Maximum number of multiple records&quot;  at a Custom Field Set creation time. After that it is only possible via database value update in the <code>civicrm_custom_group.max_multiple</code>. Out of curiosity -  why is that?</p>
  
Tags: <multi-record><multiple-records>
Title: Editable "Maximum number of multiple records" Custom Field Set option?
ThreadText: # Editable "Maximum number of multiple records" Custom Field Set option?
  
  (Asked by: username_0 on 2023-10-24)
  
  It turns out one can only edit the "Maximum number of multiple records" at a Custom Field Set creation time. After that it is only possible via database value update in the `civicrm_custom_group.max_multiple`. Out of curiosity - why is that?
  
  **Tags:** multi-record, multiple-records
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2023-10-24. Score: 3 | Accepted answer
  
  When you first create a custom group and it does not yet contain any data (e.g. no custom records have been saved for any contact) you are allowed to change anything. Once data exists, it is more restrictive to prevent data loss.
  
  However, in checking this I discovered a bug which was causing it to act stricter than it should. The logic is supposed to be that the maximum can be increased but not decreased. The bug was preventing it from being changed at all. Here is the fix: <https://github.com/civicrm/civicrm-core/pull/27916>
  
  
  ---
  
  