<!--
{
  "availability" : [
    "iOS: 8.0.0 -",
    "iPadOS: 8.0.0 -",
    "macCatalyst: 13.1.0 -",
    "macOS: 10.10.0 -",
    "tvOS: -",
    "visionOS: 1.0.0 -",
    "watchOS: 3.0.0 -"
  ],
  "documentType" : "symbol",
  "framework" : "CloudKit",
  "identifier" : "/documentation/CloudKit/CKModifyRecordsOperation/RecordSavePolicy/allKeys",
  "metadataVersion" : "0.1.0",
  "role" : "Case",
  "symbol" : {
    "kind" : "Case",
    "modules" : [
      "CloudKit"
    ],
    "preciseIdentifier" : "c:@E@CKRecordSavePolicy@CKRecordSaveAllKeys"
  },
  "title" : "CKModifyRecordsOperation.RecordSavePolicy.allKeys"
}
-->

# CKModifyRecordsOperation.RecordSavePolicy.allKeys

A policy that instructs CloudKit to save all keys of a record, even those without changes.

```
case allKeys
```

## Discussion> Important: This policy doesn’t compare record change tags. To only save changes to the most recent version of a record, use ``doc://com.apple.cloudkit/documentation/CloudKit/CKModifyRecordsOperation/RecordSavePolicy/ifServerRecordUnchanged`` instead.

This policy causes CloudKit to overwrite any existing values on the server. It’s possible for a server record to contain keys that aren’t present locally. Another client might add keys to the record after you fetch it. Also, if you use the [`desiredKeys`](/documentation/CloudKit/CKFetchRecordsOperation/desiredKeys-34l1l) property to request a subset of keys during a fetch operation, saving that same record modifies only those keys that you include in the fetch and any keys you add to the record after that.

---

Copyright &copy; 2026 Apple Inc. All rights reserved. | [Terms of Use](https://www.apple.com/legal/internet-services/terms/site.html) | [Privacy Policy](https://www.apple.com/privacy/privacy-policy)