---
url: >-
  https://canary.warp-drive.io/api/@warp-drive/legacy/compat/builders/functions/saveRecord.md
description: >-
  Deprecated legacy builder for a `store.request` config that creates, updates,
  or deletes a record through adapters, like the legacy `store.saveRecord`.
---

 

#  ~~saveRecord()~~ 

```ts
function saveRecord<T extends TypedRecordInstance>(record: T, options?: Record<string, unknown>): SaveRecordRequestInput<TypeFromInstance<T>, T>;
```

Defined in: [warp-drive-packages/legacy/src/compat/builders/save-record.ts:48](https://github.com/warp-drive-data/warp-drive/blob/48dc0d277b98008082669dadc6a52e5c5682ef8e/warp-drive-packages/legacy/src/compat/builders/save-record.ts#L48)

This function builds a request config for saving the given record (e.g. creating, updating, or deleting the record).
When passed to `store.request`, this config will result in the same behavior as a legacy `store.saveRecord` request.
Additionally, it takes the same options as `store.saveRecord`.

All `@ember-data/legacy-compat` builders exist to enable you to migrate your codebase to using the correct syntax for `store.request` while temporarily preserving legacy behaviors.
This is useful for quickly upgrading an entire app to a unified syntax while a longer incremental migration is made to shift off of adapters and serializers.
To that end, these builders are deprecated and will be removed in a future version of Ember Data.

## Type Parameters

### T

`T` *extends* [`TypedRecordInstance`](../../../../core/types/record/types/TypedRecordInstance.md)

## Parameters

### record

`T`

a record to save

### options?

[`Record`](https://www.typescriptlang.org/docs/handbook/utility-types.html#recordkeys-type)<`string`, `unknown`> = `{}`

optional, may include `adapterOptions` hash which will be passed to adapter.saveRecord

## Returns

`SaveRecordRequestInput`<[`TypeFromInstance`](../../../../core/types/record/types/TypeFromInstance.md)<`T`>, `T`>

request config

## Deprecated