---
title: Migrate to v4
skip: true
---
### Remove Form.create
Form of v4 does not need to create context by calling `Form.create()`. Form now has it's own data scope and you don't need `getFieldDecorator` anymore. Just use Form.Item directly:
```jsx
// antd v3
const Demo = ({ form: { getFieldDecorator } }) => (
{getFieldDecorator('username', {
rules: [{ required: true }],
})()}
);
const WrappedDemo = Form.create()(Demo);
```
To:
```jsx
// antd v4
const Demo = () => (
);
```
Since `Form.create()` is removed, methods like `onFieldsChange` have moved to `Form` and form state is controlled by a `fields` prop. ref [example](/components/form/#components-form-demo-global-state)。
### Form control
If you want to control form, you can use `Form.useForm()` to create Form instance for operation:
```jsx
// antd v3
const Demo = ({ form: { setFieldsValue } }) => {
React.useEffect(() => {
setFieldsValue({
username: 'Bamboo',
});
}, []);
return (
{getFieldDecorator('username', {
rules: [{ required: true }],
})()}
);
};
const WrappedDemo = Form.create()(Demo);
```
To:
```jsx
// antd v4
const Demo = () => {
const [form] = Form.useForm();
React.useEffect(() => {
form.setFieldsValue({
username: 'Bamboo',
});
}, []);
return (
);
};
```
For class component, you can use `ref` to access instance:
```jsx
// antd v4
class Demo extends React.Component {
formRef = React.createRef();
componentDidMount() {
this.formRef.current.setFieldsValue({
username: 'Bamboo',
});
}
render() {
return (
);
}
}
```
If you don't want to use the Item style, you can use `noStyle` prop to remove it:
```jsx
// antd v3
const Demo = ({ form: { setFieldsValue } }) => {
return ;
};
const WrappedDemo = Form.create()(Demo);
```
To:
```jsx
// antd v4
const Demo = () => {
return (
);
};
```
### Linkage with field
New Form uses incremental update which only updates related field. So if there is some linkage between fields or updates with the whole form, you can use [`dependencies`](/components/form/#dependencies) or [`shouldUpdate`](/components/form/#shouldUpdate) to handle that.
### replace onSubmit with onFinish
You need to listen to `onSubmit` and call `validateFields` to handle validation in old Form. New Form provides `onFinish` which will only trigger when validation has passed:
```jsx
// antd v3
const Demo = ({ form: { getFieldDecorator, validateFields } }) => {
const onSubmit = e => {
e.preventDefault();
validateFields((err, values) => {
if (!err) {
console.log('Received values of form: ', values);
}
});
};
return (
{getFieldDecorator('username', {
rules: [{ required: true }],
})()}
);
};
const WrappedDemo = Form.create()(Demo);
```
To:
```jsx
// antd v4
const Demo = () => {
const onFinish = values => {
console.log('Received values of form: ', values);
};
return (
);
};
```
## Replace validateFieldsAndScroll with scrollToField
New version recommend use `onFinish` for submit after validation. Thus `validateFieldsAndScroll` is changed to more flexible method `scrollToField`:
```jsx
// antd v3
onSubmit = () => {
form.validateFieldsAndScroll((error, values) => {
// Your logic
});
};
```
To:
```jsx
// antd v4
onFinishFailed = ({ errorFields }) => {
form.scrollToField(errorFields[0].name);
};
```
### Initialization
Besides, we move `initialValue` into Form to avoid field with same name both using `initialValue` to cause conflict:
```jsx
// antd v3
const Demo = ({ form: { getFieldDecorator } }) => (
{getFieldDecorator('username', {
rules: [{ required: true }],
initialValue: 'Bamboo',
})()}
);
const WrappedDemo = Form.create()(Demo);
```
To:
```jsx
// antd v4
const Demo = () => (
);
```
In v3, modifying the `initialValue` of un-operated field will update the field value synchronously, which is a bug. However, since it has been used as a feature for a long time, we have not fixed it. In v4, the bug has been fixed. `initialValues` only takes effect when initializing and resetting the form.
### Nested field paths using arrays
In the past versions we used `.` to represent nested paths (such as `user.name` to represent `{ user: { name: '' } }`). However, in some backend systems, `.` is also included in the variable name. This causes the user to need additional code to convert, so in the new version, nested paths are represented by arrays to avoid unexpected behavior (eg `['user', 'name']`).
Therefore, paths returned by methods such as `getFieldsError` are always in an array form for the user to handle:
```jsx
form.getFieldsError();
/*
[
{ name: ['user', 'name'], errors: [] },
{ name: ['user', 'age'], errors: ['Some error message'] },
]
*/
```
Nested field definition has changed from:
```jsx
// antd v3
{getFieldDecorator('user.0.firstname', {})()}
```
To
```jsx
// antd v4
```
Similarly using `setFieldsValue` has changed from:
```jsx
// antd v3
this.formRef.current.setFieldsValue({
'user.0.firstname': 'John',
});
```
To
```jsx
// antd v4
this.formRef.current.setFieldsValue({
user: [
{
firstname: 'John',
},
],
});
```
### Remove callback in validateFields
`validateFields` will return a Promise, so you can handle the error with `async/await` or `then/catch`. It is no longer necessary to determine if `errors` is empty:
```jsx
// antd v3
validateFields((err, value) => {
if (!err) {
// Do something with value
}
});
```
To
```jsx
// antd v4
validateFields().then(values => {
// Do something with value
});
```