Answers.Body: <p>You could do that with the API:</p>
  <pre><code>$result = civicrm_api3('Membership', 'get', [
    'sequential' =&gt; 1,
    'status_id' =&gt; &quot;Transferred&quot;,
    'options' =&gt; ['limit' =&gt; 0],
    'api.Membership.create' =&gt; ['id' =&gt; &quot;\$id&quot;, 'is_override' =&gt; 1],
  ]);
  </code></pre>
  <p>(Find all memberships with status 'Transferred' and set override)</p>
  <p>Or in Explorer:
  <a href="https://i.sstatic.net/cOiCj.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/cOiCj.png" alt="API Explorer image" /></a></p>
  <p>If you can adjust your membership status rules to avoid using status override, that would be preferable but in this case your Transferred status only applies to some membership types.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-02-04T22:04:49.863Z
Answers.Text: I don't think I'm comfortable with the API, but I can that this will work and look at how I might use this in future, when I have learnt a bit more.+
Answers.UserDisplayName: Mick Kahn
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-02-05T15:21:45.150Z
Answers.Text: I can't do this with membership status rules as it doesn't apply universally. The criteria for for being transferred can't be determined within CiviCRM. Its not event specific to certain membership types. Its not actually a one off exercise and people can also transfer back. But as in future they will all be done as one-offs the override mechanism works fine. Its just the initial batch where I want to use the bulk update.
Answers.UserDisplayName: Mick Kahn
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-02-04T09:17:33.980Z
Answers.LastActivityDate: 2021-02-04T09:17:33.980Z
Answers.UserDisplayName: Aidan
Body: <p>I've made some changes to our membership structure and will be creating new memberships for a significant number of contacts. I'd like to keep the old memberships for completeness and have created a new status of &quot;Transferred&quot; to distinguish them from normally Expired or Cancelled. I can set the status with a bulk update on the records, but I can't see a way to set the Status override field in the bulk update (it doesn't appear as an option in profiles) and I am worried that the automatic membership status check will change them to Expired.</p>
  <p>Using CiviCRM 5.26.2</p>
  
Tags: <civimember><profile>
Title: setting membership status override in bulk update
ThreadText: # setting membership status override in bulk update
  
  (Asked by: username_0 on 2021-02-03)
  
  I've made some changes to our membership structure and will be creating new memberships for a significant number of contacts. I'd like to keep the old memberships for completeness and have created a new status of "Transferred" to distinguish them from normally Expired or Cancelled. I can set the status with a bulk update on the records, but I can't see a way to set the Status override field in the bulk update (it doesn't appear as an option in profiles) and I am worried that the automatic membership status check will change them to Expired.
  
  Using CiviCRM 5.26.2
  
  **Tags:** civimember, profile
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-02-04. Score: 1
  
  You could do that with the API:
  
  ```
  $result = civicrm_api3('Membership', 'get', [
    'sequential' => 1,
    'status_id' => "Transferred",
    'options' => ['limit' => 0],
    'api.Membership.create' => ['id' => "\$id", 'is_override' => 1],
  ]);
  
  ```
  
  (Find all memberships with status 'Transferred' and set override)
  
  Or in Explorer:
  [![API Explorer image](https://i.sstatic.net/cOiCj.png)](https://i.sstatic.net/cOiCj.png)
  
  If you can adjust your membership status rules to avoid using status override, that would be preferable but in this case your Transferred status only applies to some membership types.
  
  > **Comments:**
  > **username_0**: I don't think I'm comfortable with the API, but I can that this will work and look at how I might use this in future, when I have learnt a bit more.+  
  > **username_0**: I can't do this with membership status rules as it doesn't apply universally. The criteria for for being transferred can't be determined within CiviCRM. Its not event specific to certain membership types. Its not actually a one off exercise and people can also transfer back. But as in future they will all be done as one-offs the override mechanism works fine. Its just the initial batch where I want to use the bulk update.  
  
  ---
  
  